Broadcast signal transmission apparatus, broadcast signal reception apparatus, broadcast signal transmission method, and broadcast signal reception method

ABSTRACT

The present invention proposes a method for transmitting a broadcast signal. The method for transmitting a broadcast signal according to the present invention proposes a system which may support a next generation broadcast service, in an environment supporting next generation hybrid broadcast that uses a terrestrial broadcast network and an internet network. Further, the present invention proposes an efficient signaling method which can cover both the terrestrial broadcast network and the internet network, in an environment supporting next generation hybrid broadcast.

This application is a National Stage Application of InternationalApplication No. PCT/KR2016/000544 filed on Jan. 19, 2016, and claimspriority to U.S. Provisional Application No. 62/105,750 filed on Jan.21, 2015, all of which are hereby incorporated by reference in theirentireties as if fully set forth herein.

TECHNICAL FIELD

The present invention relates to an apparatus for transmitting abroadcast signal, an apparatus for receiving a broadcast signal andmethods for transmitting and receiving a broadcast signal.

BACKGROUND ART

As analog broadcast signal transmission comes to an end, varioustechnologies for transmitting/receiving digital broadcast signals arebeing developed. A digital broadcast signal may include a larger amountof video/audio data than an analog broadcast signal and further includevarious types of additional data in addition to the video/audio data.

DISCLOSURE Technical Problem

That is, a digital broadcast system can provide HD (high definition)images, multichannel audio and various additional services. However,data transmission efficiency for transmission of large amounts of data,robustness of transmission/reception networks and network flexibility inconsideration of mobile reception equipment need to be improved fordigital broadcast.

Technical Solution

The present invention provides a system capable of effectivelysupporting future broadcast services in an environment supporting futurehybrid broadcasting using terrestrial broadcast networks and theInternet and related signaling methods.

Advantageous Effects

The present invention can control quality of service (QoS) with respectto services or service components by processing data on the basis ofservice characteristics, thereby providing various broadcast services.

The present invention can achieve transmission flexibility bytransmitting various broadcast services through the same radio frequency(RF) signal bandwidth.

The present invention can provide methods and apparatuses fortransmitting and receiving broadcast signals, which enable digitalbroadcast signals to be received without error even when a mobilereception device is used or even in an indoor environment.

The present invention can effectively support future broadcast servicesin an environment supporting future hybrid broadcasting usingterrestrial broadcast networks and the Internet.

DESCRIPTION OF DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention and are incorporated in and constitute apart of this application, illustrate embodiment(s) of the invention andtogether with the description serve to explain the principle of theinvention. In the drawings:

FIG. 1 illustrates a receiver protocol stack according to an embodimentof the present invention;

FIG. 2 illustrates a relation between an SLT and service layer signaling(SLS) according to an embodiment of the present invention;

FIG. 3 illustrates an SLT according to an embodiment of the presentinvention;

FIG. 4 illustrates SLS bootstrapping and a service discovery processaccording to an embodiment of the present invention;

FIG. 5 illustrates a USBD fragment for ROUTE/DASH according to anembodiment of the present invention;

FIG. 6 illustrates an S-TSID fragment for ROUTE/DASH according to anembodiment of the present invention;

FIG. 7 illustrates a USBD/USD fragment for MMT according to anembodiment of the present invention;

FIG. 8 illustrates a link layer protocol architecture according to anembodiment of the present invention;

FIG. 9 illustrates a structure of a base header of a link layer packetaccording to an embodiment of the present invention;

FIG. 10 illustrates a structure of an additional header of a link layerpacket according to an embodiment of the present invention;

FIG. 11 illustrates a structure of an additional header of a link layerpacket according to another embodiment of the present invention;

FIG. 12 illustrates a header structure of a link layer packet for anMPEG-2 TS packet and an encapsulation process thereof according to anembodiment of the present invention;

FIG. 13 illustrates an example of adaptation modes in IP headercompression according to an embodiment of the present invention(transmitting side);

FIG. 14 illustrates a link mapping table (LMT) and an RoHC-U descriptiontable according to an embodiment of the present invention;

FIG. 15 illustrates a structure of a link layer on a transmitter sideaccording to an embodiment of the present invention;

FIG. 16 illustrates a structure of a link layer on a receiver sideaccording to an embodiment of the present invention;

FIG. 17 illustrates a configuration of signaling transmission through alink layer according to an embodiment of the present invention(transmitting/receiving sides);

FIG. 18 is a block diagram illustrating a configuration of a broadcastsignal transmission apparatus for future broadcast services according toan embodiment of the present invention;

FIG. 19 is a block diagram illustrating a bit interleaved coding &modulation (BICM) block according to an embodiment of the presentinvention;

FIG. 20 is a block diagram illustrating a BICM block according toanother embodiment of the present invention;

FIG. 21 illustrates a bit interleaving process of physical layersignaling (PLS) according to an embodiment of the present invention;

FIG. 22 is a block diagram illustrating a configuration of a broadcastsignal reception apparatus for future broadcast services according to anembodiment of the present invention;

FIG. 23 illustrates a signaling hierarchy structure of a frame accordingto an embodiment of the present invention;

FIG. 24 is a table illustrating PLS1 data according to an embodiment ofthe present invention;

FIG. 25 is a table illustrating PLS2 data according to an embodiment ofthe present invention;

FIG. 26 is a table illustrating PLS2 data according to anotherembodiment of the present invention;

FIG. 27 illustrates a logical structure of a frame according to anembodiment of the present invention;

FIG. 28 illustrates PLS mapping according to an embodiment of thepresent invention;

FIG. 29 illustrates time interleaving according to an embodiment of thepresent invention;

FIG. 30 illustrates a basic operation of a twisted row-column blockinterleaver according to an embodiment of the present invention;

FIG. 31 illustrates an operation of a twisted row-column blockinterleaver according to another embodiment of the present invention;

FIG. 32 is a block diagram illustrating an interleaving addressgenerator including a main pseudo-random binary sequence (PRBS)generator and a sub-PRBS generator according to each FFT mode accordingto an embodiment of the present invention;

FIG. 33 illustrates a main PRBS used for all FFT modes according to anembodiment of the present invention;

FIG. 34 illustrates a sub-PRBS used for FFT modes and an interleavingaddress for frequency interleaving according to an embodiment of thepresent invention;

FIG. 35 illustrates a write operation of a time interleaver according toan embodiment of the present invention;

FIG. 36 is a table illustrating an interleaving type applied accordingto the number of PLPs;

FIG. 37 is a block diagram including a first example of a structure of ahybrid time interleaver;

FIG. 38 is a block diagram including a second example of the structureof the hybrid time interleaver;

FIG. 39 is a block diagram including a first example of a structure of ahybrid time deinterleaver;

FIG. 40 is a block diagram including a second example of the structureof the hybrid time deinterleaver;

FIG. 41 is a block diagram illustrating a hybrid broadcast receptionapparatus according to an embodiment of the present invention;

FIG. 42 is a block diagram illustrating a hybrid broadcast receiveraccording to an embodiment of the present invention;

FIG. 43 illustrates a protocol stack of a future hybrid broadcast systemaccording to an embodiment of the present invention;

FIG. 44 illustrates a structure of a transport frame delivered to aphysical layer of a future broadcast transmission system according to anembodiment of the present invention;

FIG. 45 illustrates a transport packet of an application layer transportprotocol according to an embodiment of the present invention;

FIG. 46 illustrates a method for transmitting signaling data by a futurebroadcast system according to an embodiment of the present invention;

FIG. 47 illustrates signaling data transmitted, for fast broadcastservice scan of a receiver, by the future broadcast system according toan embodiment of the present invention;

FIG. 48 illustrates signaling data transmitted, for fast broadcastservice scan of the receiver, by the future broadcast system accordingto an embodiment of the present invention;

FIG. 49 illustrates a method for transmitting FIC based signalingaccording to an embodiment of the present invention;

FIG. 50 illustrates signaling data transmitted, for fast broadcastservice scan of the receiver, by the future broadcast system accordingto an embodiment of the present invention;

FIG. 51 illustrates a method for transmitting FIC based signalingaccording to another embodiment of the present invention;

FIG. 52 illustrates a service signaling message format of the futurebroadcast system according to an embodiment of the present invention;

FIG. 53 shows service signaling tables used in the future broadcastsystem according to an embodiment of the present invention;

FIG. 54 shows a service mapping table used in the future broadcastsystem according to an embodiment of the present invention;

FIG. 55 shows a service signaling table used in the future broadcastsystem according to an embodiment of the present invention;

FIG. 56 shows a component mapping table used in the future broadcastsystem according to an embodiment of the present invention;

FIG. 57 illustrates component mapping table description according to anembodiment of the present invention;

FIG. 58 illustrates a syntax of the component mapping table of thefuture broadcast system according to an embodiment of the presentinvention;

FIG. 59 illustrates a method for transmitting signaling related to eachservice through a broadband network in the future broadcast systemaccording to an embodiment of the present invention;

FIG. 60 illustrates a method for signaling an MPD in the futurebroadcast system according to an embodiment of the present invention;

FIG. 61 illustrates a syntax of an MPD delivery table used in the futurebroadcast system according to an embodiment of the present invention;

FIG. 62 illustrates transport session instance description of the futurebroadcast system according to an embodiment of the present invention;

FIG. 63 illustrates a SourceFlow element of the future broadcast systemaccording to an embodiment of the present invention;

FIG. 64 illustrates an EFDT of the future broadcast system according toan embodiment of the present invention;

FIG. 65 illustrates a method for transmitting an ISDT used by the futurebroadcast system according to an embodiment of the present invention;

FIG. 66 illustrates a signaling message delivery structure of the futurebroadcast system according to an embodiment of the present invention;

FIG. 67 illustrates signaling data transmitted, for fast broadcastservice scan of the receiver, by the future broadcast system accordingto an embodiment of the present invention;

FIG. 68 illustrates signaling data transmitted, for fast broadcastservice scan of the receiver, by the future broadcast system accordingto an embodiment of the present invention;

FIG. 69 illustrates component mapping table description according to anembodiment of the present invention;

FIG. 70 illustrates a component mapping table description according toan embodiment of the present invention;

FIGS. 71 and 72 illustrate component mapping table description accordingto an embodiment of the present invention;

FIG. 73 illustrates component mapping table description according to anembodiment of the present invention;

FIG. 74 illustrates common attributes and elements of an MPD accordingto an embodiment of the present invention;

FIG. 75 illustrates transport session instance description according toan embodiment of the present invention;

FIG. 76 illustrates a SourceFlow element of the future broadcast systemaccording to an embodiment of the present invention;

FIG. 77 illustrates signaling data transmitted, for fast broadcastservice scan of a receiver, by a future broadcast system according toanother embodiment of the present invention;

FIG. 78 illustrates signaling data transmitted, for fast broadcastservice scan of the receiver, by a future broadcast system according toanother embodiment of the present invention;

FIG. 79 illustrates a method for acquiring service layer signaling inthe future broadcast system according to an embodiment of the presentinvention;

FIG. 80 illustrates a method for acquiring service layer signaling andlink layer signaling in the future broadcast system according to anembodiment of the present invention;

FIG. 81 illustrates a method for acquiring service layer signaling inthe future broadcast system according to an embodiment of the presentinvention;

FIG. 82 illustrates a method for acquiring service layer signaling andlink layer signaling in the future broadcast system according to anembodiment of the present invention;

FIG. 83 illustrates a method for delivering service layer signaling inthe future broadcast system according to an embodiment of the presentinvention;

FIG. 84 illustrates a method for delivering service layer signaling andlink layer signaling in the future broadcast system according to anembodiment of the present invention;

FIG. 85 illustrates a method for delivering service layer signaling inthe future broadcast system according to an embodiment of the presentinvention;

FIG. 86 illustrates a method for delivering service layer signaling andlink layer signaling in the future broadcast system according to anembodiment of the present invention;

FIG. 87 illustrates a method for transmitting service layer signaling inthe future broadcast system according to an embodiment of the presentinvention;

FIG. 88 illustrates a method for delivering service layer signaling inthe future broadcast system according to an embodiment of the presentinvention;

FIG. 89 illustrates a syntax of a header of a signaling messageaccording to another embodiment of the present invention;

FIG. 90 illustrates a protocol stack which processes a DASHinitialization segment according to an embodiment of the presentinvention;

FIG. 91 illustrates part of layered coding transport (LCT) sessioninstance description (LSID) according to an embodiment of the presentinvention;

FIG. 92 illustrates signaling object description (SOD) providinginformation for filtering a service signaling message according to anembodiment of the present invention;

FIG. 93 illustrates an object including a signaling message according toan embodiment of the present invention;

FIG. 94 illustrates TOI configuration description (TCD) according to anembodiment of the present invention;

FIG. 95 illustrates a payload format element of a transport packetaccording to an embodiment of the present invention;

FIG. 96 illustrates TOI configuration instance description (TCD)according to an embodiment of the present invention;

FIG. 97 illustrates a syntax of a payload of a fast information channel(FIC) according to an embodiment of the present invention;

FIG. 98 illustrates a syntax of a payload of an FIC according to anotherembodiment of the present invention;

FIG. 99 illustrates a syntax of serving level signaling according toanother embodiment of the present invention;

FIG. 100 illustrates component mapping description according to anotherembodiment of the present invention;

FIG. 101 illustrates a syntax of URL signaling description according toanother embodiment of the present invention;

FIG. 102 illustrates a SourceFlow element according to anotherembodiment of the present invention;

FIG. 103 illustrates a process of acquiring signaling informationthrough a broadcast network according to another embodiment of thepresent invention;

FIG. 104 illustrates a process of acquiring signaling informationthrough a broadcast network and a broadband network according to anotherembodiment of the present invention;

FIG. 105 illustrates a process of acquiring signaling informationthrough a broadband network according to another embodiment of thepresent invention;

FIG. 106 illustrates a process of acquiring an electronic service guide(ESG) through a broadcast network according to another embodiment of thepresent invention;

FIG. 107 illustrates a process of acquiring video segments and audiosegments of broadcast services through a broadcast network according toanother embodiment of the present invention;

FIG. 108 illustrates a process of acquiring video segments through abroadcast network and acquiring audio segments through a broadbandnetwork according to another embodiment of the present invention;

FIG. 109 is a diagram showing the syntax of a payload of a FIC accordingto another embodiment of the present invention;

FIG. 110 is a diagram showing the syntax of a payload of a FIC accordingto another embodiment of the present invention;

FIG. 111 is a diagram showing a transport_parameter_descriptor accordingto an embodiment of the present invention;

FIG. 112 is a diagram showing a signaling structure in a process ofacquiring a broadcast service at a receiver according to anotherembodiment of the present invention;

FIG. 113 is a flowchart illustrating a process of transmitting andprocessing a broadcast signal according to an embodiment of the presentinvention;

FIG. 114 is a diagram showing an apparatus for processing a broadcastsignal according to an embodiment of the present invention;

FIG. 115 is a diagram showing some of fast information channel (FIC)data according to another embodiment of the present invention;

FIG. 116 is a diagram showing the other of the FIC data according toanother embodiment of the present invention;

FIG. 117 is a diagram showing some of fast information channel (FIC)data according to another embodiment of the present invention;

FIG. 118 is a diagram showing the other of the FIC data according toanother embodiment of the present invention;

FIG. 119 is a diagram showing some of fast information channel (FIC)data according to another embodiment of the present invention;

FIG. 120 is a diagram showing the other of the FIC data according toanother embodiment of the present invention;

FIG. 121 is a diagram illustrating a method of processing service dataaccording to an embodiment of the present invention; and

FIG. 122 is a diagram showing an apparatus for processing service dataaccording to an embodiment of the present invention.

BEST MODE

Reference will now be made in detail to the preferred embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. The detailed description, which will be given below withreference to the accompanying drawings, is intended to explain exemplaryembodiments of the present invention, rather than to show the onlyembodiments that can be implemented according to the present invention.The following detailed description includes specific details in order toprovide a thorough understanding of the present invention. However, itwill be apparent to those skilled in the art that the present inventionmay be practiced without such specific details.

Although the terms used in the present invention are selected fromgenerally known and used terms, some of the terms mentioned in thedescription of the present invention have been selected by the applicantat his or her discretion, the detailed meanings of which are describedin relevant parts of the description herein. Furthermore, it is requiredthat the present invention is understood, not simply by the actual termsused but by the meanings of each term lying within.

The present invention provides apparatuses and methods for transmittingand receiving broadcast signals for future broadcast services. Futurebroadcast services according to an embodiment of the present inventioninclude a terrestrial broadcast service, a mobile broadcast service, anultra high definition television (UHDTV) service, etc. The presentinvention may process broadcast signals for the future broadcastservices through non-MIMO (Multiple Input Multiple Output) or MIMOaccording to one embodiment. A non-MIMO scheme according to anembodiment of the present invention may include a MISO (Multiple InputSingle Output) scheme, a SISO (Single Input Single Output) scheme, etc.

FIG. 1 illustrates a receiver protocol stack according to an embodimentof the present invention.

Two schemes may be used in broadcast service delivery through abroadcast network.

In a first scheme, media processing units (MPUs) are transmitted usingan MMT protocol (MMTP) based on MPEG media transport (MMT). In a secondscheme, dynamic adaptive streaming over HTTP (DASH) segments may betransmitted using real time object delivery over unidirectionaltransport (ROUTE) based on MPEG DASH.

Non-timed content including NRT media, EPG data, and other files isdelivered with ROUTE. Signaling may be delivered over MMTP and/or ROUTE,while bootstrap signaling information is provided by the means of theService List Table (SLT).

In hybrid service delivery, MPEG DASH over HTTP/TCP/IP is used on thebroadband side. Media files in ISO Base Media File Format (BMFF) areused as the delivery, media encapsulation and synchronization format forboth broadcast and broadband delivery. Here, hybrid service delivery mayrefer to a case in which one or more program elements are deliveredthrough a broadband path.

Services are delivered using three functional layers. These are thephysical layer, the delivery layer and the service management layer. Thephysical layer provides the mechanism by which signaling, serviceannouncement and IP packet streams are transported over the broadcastphysical layer and/or broadband physical layer. The delivery layerprovides object and object flow transport functionality. It is enabledby the MMTP or the ROUTE protocol, operating on a UDP/IP multicast overthe broadcast physical layer, and enabled by the HTTP protocol on aTCP/IP unicast over the broadband physical layer. The service managementlayer enables any type of service, such as linear TV or HTML5application service, to be carried by the underlying delivery andphysical layers.

In this figure, a protocol stack part on a broadcast side may be dividedinto a part transmitted through the SLT and the MMTP, and a parttransmitted through ROUTE.

The SLT may be encapsulated through UDP and IP layers. Here, the SLTwill be described below. The MMTP may transmit data formatted in an MPUformat defined in MMT, and signaling information according to the MMTP.The data may be encapsulated through the UDP and IP layers. ROUTE maytransmit data formatted in a DASH segment form, signaling information,and non-timed data such as NRT data, etc. The data may be encapsulatedthrough the UDP and IP layers. According to a given embodiment, some orall processing according to the UDP and IP layers may be omitted. Here,the illustrated signaling information may be signaling informationrelated to a service.

The part transmitted through the SLT and the MMTP and the parttransmitted through ROUTE may be processed in the UDP and IP layers, andthen encapsulated again in a data link layer. The link layer will bedescribed below. Broadcast data processed in the link layer may bemulticast as a broadcast signal through processes such asencoding/interleaving, etc. in the physical layer.

In this figure, a protocol stack part on a broadband side may betransmitted through HTTP as described above. Data formatted in a DASHsegment form, signaling information, NRT information, etc. may betransmitted through HTTP. Here, the illustrated signaling informationmay be signaling information related to a service. The data may beprocessed through the TCP layer and the IP layer, and then encapsulatedinto the link layer. According to a given embodiment, some or all of theTCP, the IP, and the link layer may be omitted. Broadband data processedthereafter may be transmitted by unicast in the broadband through aprocess for transmission in the physical layer.

Service can be a collection of media components presented to the user inaggregate; components can be of multiple media types; a Service can beeither continuous or intermittent; a Service can be Real Time orNon-Real Time; Real Time Service can consist of a sequence of TVprograms.

FIG. 2 illustrates a relation between the SLT and SLS according to anembodiment of the present invention.

Service signaling provides service discovery and descriptioninformation, and comprises two functional components: Bootstrapsignaling via the Service List Table (SLT) and the Service LayerSignaling (SLS). These represent the information which is necessary todiscover and acquire user services. The SLT enables the receiver tobuild a basic service list, and bootstrap the discovery of the SLS foreach service.

The SLT can enable very rapid acquisition of basic service information.The SLS enables the receiver to discover and access services and theircontent components. Details of the SLT and SLS will be described below.

As described in the foregoing, the SLT may be transmitted throughUDP/IP. In this instance, according to a given embodiment, datacorresponding to the SLT may be delivered through the most robust schemein this transmission.

The SLT may have access information for accessing SLS delivered by theROUTE protocol. In other words, the SLT may be bootstrapped into SLSaccording to the ROUTE protocol. The SLS is signaling informationpositioned in an upper layer of ROUTE in the above-described protocolstack, and may be delivered through ROUTE/UDP/IP. The SLS may betransmitted through one of LCT sessions included in a ROUTE session. Itis possible to access a service component corresponding to a desiredservice using the SLS.

In addition, the SLT may have access information for accessing an MMTsignaling component delivered by MMTP. In other words, the SLT may bebootstrapped into SLS according to the MMTP. The SLS may be delivered byan MMTP signaling message defined in MMT. It is possible to access astreaming service component (MPU) corresponding to a desired serviceusing the SLS. As described in the foregoing, in the present invention,an NRT service component is delivered through the ROUTE protocol, andthe SLS according to the MMTP may include information for accessing theROUTE protocol. In broadband delivery, the SLS is carried overHTTP(S)/TCP/IP.

FIG. 3 illustrates an SLT according to an embodiment of the presentinvention.

First, a description will be given of a relation among respectivelogical entities of service management, delivery, and a physical layer.

Services may be signaled as being one of two basic types. First type isa linear audio/video or audio-only service that may have an app-basedenhancement. Second type is a service whose presentation and compositionis controlled by a downloaded application that is executed uponacquisition of the service. The latter can be called an “app-based”service.

The rules regarding presence of ROUTE/LCT sessions and/or MMTP sessionsfor carrying the content components of a service may be as follows.

For broadcast delivery of a linear service without app-basedenhancement, the service's content components can be carried by either(but not both): (1) one or more ROUTE/LCT sessions, or (2) one or moreMMTP sessions.

For broadcast delivery of a linear service with app-based enhancement,the service's content components can be carried by: (1) one or moreROUTE/LCT sessions, and (2) zero or more MMTP sessions.

In certain embodiments, use of both MMTP and ROUTE for streaming mediacomponents in the same service may not be allowed.

For broadcast delivery of an app-based service, the service's contentcomponents can be carried by one or more ROUTE/LCT sessions.

Each ROUTE session comprises one or more LCT sessions which carry as awhole, or in part, the content components that make up the service. Instreaming services delivery, an LCT session may carry an individualcomponent of a user service such as an audio, video or closed captionstream. Streaming media is formatted as DASH Segments.

Each MMTP session comprises one or more MMTP packet flows which carryMMT signaling messages or as a whole, or in part, the content component.An MMTP packet flow may carry MMT signaling messages or componentsformatted as MPUs.

For the delivery of NRT User Services or system metadata, an LCT sessioncarries file-based content items. These content files may consist ofcontinuous (time-based) or discrete (non-time-based) media components ofan NRT service, or metadata such as Service Signaling or ESG fragments.Delivery of system metadata such as service signaling or ESG fragmentsmay also be achieved through the signaling message mode of MMTP.

A broadcast stream is the abstraction for an RF channel, which isdefined in terms of a carrier frequency centered within a specifiedbandwidth. It is identified by the pair [geographic area, frequency]. Aphysical layer pipe (PLP) corresponds to a portion of the RF channelEach PLP has certain modulation and coding parameters. It is identifiedby a PLP identifier (PLPID), which is unique within the broadcast streamit belongs to. Here, PLP can be referred to as DP (data pipe).

Each service is identified by two forms of service identifier: a compactform that is used in the SLT and is unique only within the broadcastarea; and a globally unique form that is used in the SLS and the ESG. AROUTE session is identified by a source IP address, destination IPaddress and destination port number. An LCT session (associated with theservice component(s) it carries) is identified by a transport sessionidentifier (TSI) which is unique within the scope of the parent ROUTEsession. Properties common to the LCT sessions, and certain propertiesunique to individual LCT sessions, are given in a ROUTE signalingstructure called a service-based transport session instance description(S-TSID), which is part of the service layer signaling. Each LCT sessionis carried over a single physical layer pipe. According to a givenembodiment, one LCT session may be transmitted through a plurality ofPLPs. Different LCT sessions of a ROUTE session may or may not becontained in different physical layer pipes. Here, the ROUTE session maybe delivered through a plurality of PLPs. The properties described inthe S-TSID include the TSI value and PLPID for each LCT session,descriptors for the delivery objects/files, and application layer FECparameters.

A MMTP session is identified by destination IP address and destinationport number. An MMTP packet flow (associated with the servicecomponent(s) it carries) is identified by a packet_id which is uniquewithin the scope of the parent MMTP session. Properties common to eachMMTP packet flow, and certain properties of MMTP packet flows, are givenin the SLT. Properties for each MMTP session are given by MMT signalingmessages, which may be carried within the MMTP session. Different MMTPpacket flows of a MMTP session may or may not be contained in differentphysical layer pipes. Here, the MMTP session may be delivered through aplurality of PLPs. The properties described in the MMT signalingmessages include the packet_id value and PLPID for each MMTP packetflow. Here, the MMT signaling messages may have a form defined in MMT,or have a deformed form according to embodiments to be described below.

Hereinafter, a description will be given of low level signaling (LLS).

Signaling information which is carried in the payload of IP packets witha well-known address/port dedicated to this function is referred to aslow level signaling (LLS). The IP address and the port number may bedifferently configured depending on embodiments. In one embodiment, LLScan be transported in IP packets with address 224.0.23.60 anddestination port 4937/udp. LLS may be positioned in a portion expressedby “SLT” on the above-described protocol stack. However, according to agiven embodiment, the LLS may be transmitted through a separate physicalchannel (dedicated channel) in a signal frame without being subjected toprocessing of the UDP/IP layer.

UDP/IP packets that deliver LLS data may be formatted in a form referredto as an LLS table. A first byte of each UDP/IP packet that delivers theLLS data may correspond to a start of the LLS table. The maximum lengthof any LLS table is limited by the largest IP packet that can bedelivered from the PHY layer, 65,507 bytes.

The LLS table may include an LLS table ID field that identifies a typeof the LLS table, and an LLS table version field that identifies aversion of the LLS table. According to a value indicated by the LLStable ID field, the LLS table may include the above-described SLT or arating region table (RRT). The RRT may have information about contentadvisory rating.

Hereinafter, the SLT will be described. LLS can be signaling informationwhich supports rapid channel scans and bootstrapping of serviceacquisition by the receiver, and SLT can be a table of signalinginformation which is used to build a basic service listing and providebootstrap discovery of SLS.

The function of the SLT is similar to that of the program associationtable (PAT) in MPEG-2 Systems, and the fast information channel (FIC)found in ATSC Systems. For a receiver first encountering the broadcastemission, this is the place to start. SLT supports a rapid channel scanwhich allows a receiver to build a list of all the services it canreceive, with their channel name, channel number, etc., and SLT providesbootstrap information that allows a receiver to discover the SLS foreach service. For ROUTE/DASH-delivered services, the bootstrapinformation includes the destination IP address and destination port ofthe LCT session that carries the SLS. For MMT/MPU-delivered services,the bootstrap information includes the destination IP address anddestination port of the MMTP session carrying the SLS.

The SLT supports rapid channel scans and service acquisition byincluding the following information about each service in the broadcaststream. First, the SLT can include information necessary to allow thepresentation of a service list that is meaningful to viewers and thatcan support initial service selection via channel number or up/downselection. Second, the SLT can include information necessary to locatethe service layer signaling for each service listed. That is, the SLTmay include access information related to a location at which the SLS isdelivered.

The illustrated SLT according to the present embodiment is expressed asan XML document having an SLT root element. According to a givenembodiment, the SLT may be expressed in a binary format or an XMLdocument.

The SLT root element of the SLT illustrated in the figure may include@bsid, @sltSectionVersion, @sltSectionNumber, @totalSltSectionNumbers,@language, @capabilities, InetSigLoc and/or Service. According to agiven embodiment, the SLT root element may further include @providerId.According to a given embodiment, the SLT root element may not include@language.

The service element may include @serviceId, @SLTserviceSeqNumber,@protected, @majorChannelNo, @minorChannelNo, @serviceCategory,@shortServiceName, @hidden, @slsProtocolType, BroadcastSignaling,@slsPlpId, @slsDestinationIpAddress, @slsDestinationUdpPort,@slsSourceIpAddress, @slsMajorProtocolVersion, @SlsMinorProtocolVersion,@serviceLanguage, @broadbandAccessRequired, @capabilities and/orInetSigLoc.

According to a given embodiment, an attribute or an element of the SLTmay be added/changed/deleted. Each element included in the SLT mayadditionally have a separate attribute or element, and some attribute orelements according to the present embodiment may be omitted. Here, afield which is marked with @ may correspond to an attribute, and a fieldwhich is not marked with @ may correspond to an element.

@bsid is an identifier of the whole broadcast stream. The value of BSIDmay be unique on a regional level.

@providerId can be an index of broadcaster that is using part or all ofthis broadcast stream. This is an optional attribute. When it's notpresent, it means that this broadcast stream is being used by onebroadcaster. @providerId is not illustrated in the figure.

@sltSectionVersion can be a version number of the SLT section. ThesltSectionVersion can be incremented by 1 when a change in theinformation carried within the slt occurs. When it reaches maximumvalue, it wraps around to 0.

@sltSectionNumber can be the number, counting from 1, of this section ofthe SLT. In other words, @sltSectionNumber may correspond to a sectionnumber of the SLT section. When this field is not used,@sltSectionNumber may be set to a default value of 1.

@totalSltSectionNumbers can be the total number of sections (that is,the section with the highest sltSectionNumber) of the SLT of which thissection is part. sltSectionNumber and totalSltSectionNumbers togethercan be considered to indicate “Part M of N” of one portion of the SLTwhen it is sent in fragments. In other words, when the SLT istransmitted, transmission through fragmentation may be supported. Whenthis field is not used, @totalSltSectionNumbers may be set to a defaultvalue of 1. A case in which this field is not used may correspond to acase in which the SLT is not transmitted by being fragmented.

@language can indicate primary language of the services included in thisslt instance. According to a given embodiment, a value of this field mayhave be a three-character language code defined in the ISO. This fieldmay be omitted.

@capabilities can indicate required capabilities for decoding andmeaningfully presenting the content for all the services in this sltinstance.

InetSigLoc can provide a URL telling the receiver where it can acquireany requested type of data from external server(s) via broadband. Thiselement may include @urlType as a lower field. According to a value ofthe @urlType field, a type of a URL provided by InetSigLoc may beindicated. According to a given embodiment, when the @urlType field hasa value of 0, InetSigLoc may provide a URL of a signaling server. Whenthe @urlType field has a value of 1, InetSigLoc may provide a URL of anESG server. When the @urlType field has other values, the field may bereserved for future use.

The service field is an element having information about each service,and may correspond to a service entry. Service element fieldscorresponding to the number of services indicated by the SLT may bepresent. Hereinafter, a description will be given of a lowerattribute/element of the service field.

@serviceId can be an integer number that uniquely identify this servicewithin the scope of this broadcast area. According to a givenembodiment, a scope of @serviceId may be changed. @SLTserviceSeqNumbercan be an integer number that indicates the sequence number of the SLTservice information with service ID equal to the serviceId attributeabove. SLTserviceSeqNumber value can start at 0 for each service and canbe incremented by 1 every time any attribute in this service element ischanged. If no attribute values are changed compared to the previousService element with a particular value of ServiceID thenSLTserviceSeqNumber would not be incremented. The SLTserviceSeqNumberfield wraps back to 0 after reaching the maximum value.

@protected is flag information which may indicate whether one or morecomponents for significant reproduction of the service are in aprotected state. When set to “1” (true), that one or more componentsnecessary for meaningful presentation is protected. When set to “0”(false), this flag indicates that no components necessary for meaningfulpresentation of the service are protected. Default value is false.

@majorChannelNo is an integer number representing the “major” channelnumber of the service. An example of the field may have a range of 1 to999.

@minorChannelNo is an integer number representing the “minor” channelnumber of the service. An example of the field may have a range of 1 to999.

@serviceCategory can indicate the category of this service. This fieldmay indicate a type that varies depending on embodiments. According to agiven embodiment, when this field has values of 1, 2, and 3, the valuesmay correspond to a linear A/V service, a linear audio only service, andan app-based service, respectively. When this field has a value of 0,the value may correspond to a service of an undefined category. Whenthis field has other values except for 1, 2, and 3, the field may bereserved for future use. @shortServiceName can be a short string name ofthe Service.

@hidden can be boolean value that when present and set to “true”indicates that the service is intended for testing or proprietary use,and is not to be selected by ordinary TV receivers. The default value is“false” when not present.

@ slsProtocolType can be an attribute indicating the type of protocol ofService Layer Signaling used by this service. This field may indicate atype that varies depending on embodiments. According to a givenembodiment, when this field has values of 1 and 2, protocols of SLS usedby respective corresponding services may be ROUTE and MMTP,respectively. When this field has other values except for 0, the fieldmay be reserved for future use. This field may be referred to as@slsProtocol.

BroadcastSignaling and lower attributes/elements thereof may provideinformation related to broadcast signaling. When the BroadcastSignalingelement is not present, the child element InetSigLoc of the parentservice element can be present and its attribute urlType includesURL_type 0x00 (URL to signaling server). In this case attribute urlsupports the query parameter svc=<service_id> where service_idcorresponds to the serviceId attribute for the parent service element.

Alternatively when the BroadcastSignaling element is not present, theelement InetSigLoc can be present as a child element of the slt rootelement and the attribute urlType of that InetSigLoc element includesURL_type 0x00 (URL to signaling server). In this case, attribute url forURL_type 0x00 supports the query parameter svc=<service_id> whereservice_id corresponds to the serviceId attribute for the parent Serviceelement.

@slsPlpId can be a string representing an integer number indicating thePLP ID of the physical layer pipe carrying the SLS for this service.

@slsDestinationIpAddress can be a string containing the dotted-IPv4destination address of the packets carrying SLS data for this service.

@slsDestinationUdpPort can be a string containing the port number of thepackets carrying SLS data for this service. As described in theforegoing, SLS bootstrapping may be performed by destination IP/UDPinformation.

@slsSourceIpAddress can be a string containing the dotted-IPv4 sourceaddress of the packets carrying SLS data for this service.

@slsMajorProtocolVersion can be major version number of the protocolused to deliver the service layer signaling for this service. Defaultvalue is 1.

@SlsMinorProtocolVersion can be minor version number of the protocolused to deliver the service layer signaling for this service. Defaultvalue is 0.

@serviceLanguage can be a three-character language code indicating theprimary language of the service. A value of this field may have a formthat varies depending on embodiments.

@broadbandAccessRequired can be a Boolean indicating that broadbandaccess is required for a receiver to make a meaningful presentation ofthe service. Default value is false. When this field has a value ofTrue, the receiver needs to access a broadband for significant servicereproduction, which may correspond to a case of hybrid service delivery.

@capabilities can represent required capabilities for decoding andmeaningfully presenting the content for the service with service IDequal to the service Id attribute above.

InetSigLoc can provide a URL for access to signaling or announcementinformation via broadband, if available. Its data type can be anextension of the any URL data type, adding an @urlType attribute thatindicates what the URL gives access to. An @urlType field of this fieldmay indicate the same meaning as that of the @urlType field ofInetSigLoc described above. When an InetSigLoc element of attributeURL_type 0x00 is present as an element of the SLT, it can be used tomake HTTP requests for signaling metadata. The HTTP POST message bodymay include a service term. When the InetSigLoc element appears at thesection level, the service term is used to indicate the service to whichthe requested signaling metadata objects apply. If the service term isnot present, then the signaling metadata objects for all services in thesection are requested. When the InetSigLoc appears at the service level,then no service term is needed to designate the desired service. When anInetSigLoc element of attribute URL_type 0x01 is provided, it can beused to retrieve ESG data via broadband. If the element appears as achild element of the service element, then the URL can be used toretrieve ESG data for that service. If the element appears as a childelement of the SLT element, then the URL can be used to retrieve ESGdata for all services in that section.

In another example of the SLT, @sltSectionVersion, @sltSectionNumber,@totalSltSectionNumbers and/or @language fields of the SLT may beomitted

In addition, the above-described InetSigLoc field may be replaced by@sltInetSigUri and/or @sltInetEsgUri field. The two fields may includethe URI of the signaling server and URI information of the ESG server,respectively. The InetSigLoc field corresponding to a lower field of theSLT and the InetSigLoc field corresponding to a lower field of theservice field may be replaced in a similar manner.

The suggested default values may vary depending on embodiments. Anillustrated “use” column relates to the respective fields. Here, “1” mayindicate that a corresponding field is an essential field, and “0 . . .1” may indicate that a corresponding field is an optional field.

FIG. 4 illustrates SLS bootstrapping and a service discovery processaccording to an embodiment of the present invention.

Hereinafter, SLS will be described.

SLS can be signaling which provides information for discovery andacquisition of services and their content components.

For ROUTE/DASH, the SLS for each service describes characteristics ofthe service, such as a list of its components and where to acquire them,and the receiver capabilities required to make a meaningful presentationof the service. In the ROUTE/DASH system, the SLS includes the userservice bundle description (USBD), the S-TSID and the DASH mediapresentation description (MPD). Here, USBD or user service description(USD) is one of SLS XML fragments, and may function as a signaling herbthat describes specific descriptive information. USBD/USD may beextended beyond 3GPP MBMS. Details of USBD/USD will be described below.

The service signaling focuses on basic attributes of the service itself,especially those attributes needed to acquire the service. Properties ofthe service and programming that are intended for viewers appear asservice announcement, or ESG data.

Having separate Service Signaling for each service permits a receiver toacquire the appropriate SLS for a service of interest without the needto parse the entire SLS carried within a broadcast stream.

For optional broadband delivery of Service Signaling, the SLT caninclude HTTP URLs where the Service Signaling files can be obtained, asdescribed above.

LLS is used for bootstrapping SLS acquisition, and subsequently, the SLSis used to acquire service components delivered on either ROUTE sessionsor MMTP sessions. The described figure illustrates the followingsignaling sequences. Receiver starts acquiring the SLT described above.Each service identified by service_id delivered over ROUTE sessionsprovides SLS bootstrapping information: PLPID(#1), source IP address(sIP1), destination IP address (dIP1), and destination port number(dPort1). Each service identified by service_id delivered over MMTPsessions provides SLS bootstrapping information: PLPID(#2), destinationIP address (dIP2), and destination port number (dPort2).

For streaming services delivery using ROUTE, the receiver can acquireSLS fragments carried over the IP/UDP/LCT session and PLP; whereas forstreaming services delivery using MMTP, the receiver can acquire SLSfragments carried over an MMTP session and PLP. For service deliveryusing ROUTE, these SLS fragments include USBD/USD fragments, S-TSIDfragments, and MPD fragments. They are relevant to one service. USBD/USDfragments describe service layer properties and provide URI referencesto S-TSID fragments and URI references to MPD fragments. In other words,the USBD/USD may refer to S-TSID and MPD. For service delivery usingMMTP, the USBD references the MMT signaling's MPT message, the MP Tableof which provides identification of package ID and location informationfor assets belonging to the service. Here, an asset is a multimedia dataentity, and may refer to a data entity which is combined into one uniqueID and is used to generate one multimedia presentation. The asset maycorrespond to a service component included in one service. The MPTmessage is a message having the MP table of MMT. Here, the MP table maybe an MMT package table having information about content and an MMTasset. Details may be similar to a definition in MMT. Here, mediapresentation may correspond to a collection of data that establishesbounded/unbounded presentation of media content.

The S-TSID fragment provides component acquisition informationassociated with one service and mapping between DASH Representationsfound in the MPD and in the TSI corresponding to the component of theservice. The S-TSID can provide component acquisition information in theform of a TSI and the associated DASH representation identifier, andPLPID carrying DASH segments associated with the DASH representation. Bythe PLPID and TSI values, the receiver collects the audio/videocomponents from the service and begins buffering DASH media segmentsthen applies the appropriate decoding processes.

For USBD listing service components delivered on MMTP sessions, asillustrated by “Service #2” in the described figure, the receiver alsoacquires an MPT message with matching MMT_package_id to complete theSLS. An MPT message provides the full list of service componentscomprising a service and the acquisition information for each component.Component acquisition information includes MMTP session information, thePLPID carrying the session and the packet_id within that session.

According to a given embodiment, for example, in ROUTE, two or moreS-TSID fragments may be used. Each fragment may provide accessinformation related to LCT sessions delivering content of each service.

In ROUTE, S-TSID, USBD/USD, MPD, or an LCT session delivering S-TSID,USBD/USD or MPD may be referred to as a service signaling channel. InMMTP, USBD/UD, an MMT signaling message, or a packet flow delivering theMMTP or USBD/UD may be referred to as a service signaling channel.

Unlike the illustrated example, one ROUTE or MMTP session may bedelivered through a plurality of PLPs. In other words, one service maybe delivered through one or more PLPs. As described in the foregoing,one LCT session may be delivered through one PLP. Unlike the figure,according to a given embodiment, components included in one service maybe delivered through different ROUTE sessions. In addition, according toa given embodiment, components included in one service may be deliveredthrough different MMTP sessions. According to a given embodiment,components included in one service may be delivered separately through aROUTE session and an MMTP session. Although not illustrated, componentsincluded in one service may be delivered via broadband (hybriddelivery).

FIG. 5 illustrates a USBD fragment for ROUTE/DASH according to anembodiment of the present invention.

Hereinafter, a description will be given of SLS in delivery based onROUTE.

SLS provides detailed technical information to the receiver to enablethe discovery and access of services and their content components. Itcan include a set of XML-encoded metadata fragments carried over adedicated LCT session. That LCT session can be acquired using thebootstrap information contained in the SLT as described above. The SLSis defined on a per-service level, and it describes the characteristicsand access information of the service, such as a list of its contentcomponents and how to acquire them, and the receiver capabilitiesrequired to make a meaningful presentation of the service. In theROUTE/DASH system, for linear services delivery, the SLS consists of thefollowing metadata fragments: USBD, S-TSID and the DASH MPD. The SLSfragments can be delivered on a dedicated LCT transport session withTSI=0. According to a given embodiment, a TSI of a particular LCTsession (dedicated LCT session) in which an SLS fragment is deliveredmay have a different value. According to a given embodiment, an LCTsession in which an SLS fragment is delivered may be signaled using theSLT or another scheme.

ROUTE/DASH SLS can include the user service bundle description (USBD)and service-based transport session instance description (S-TSID)metadata fragments. These service signaling fragments are applicable toboth linear and application-based services. The USBD fragment containsservice identification, device capabilities information, references toother SLS fragments required to access the service and constituent mediacomponents, and metadata to enable the receiver to determine thetransport mode (broadcast and/or broadband) of service components. TheS-TSID fragment, referenced by the USBD, provides transport sessiondescriptions for the one or more ROUTE/LCT sessions in which the mediacontent components of a service are delivered, and descriptions of thedelivery objects carried in those LCT sessions. The USBD and S-TSID willbe described below.

In streaming content signaling in ROUTE-based delivery, a streamingcontent signaling component of SLS corresponds to an MPD fragment. TheMPD is typically associated with linear services for the delivery ofDASH Segments as streaming content. The MPD provides the resourceidentifiers for individual media components of the linear/streamingservice in the form of Segment URLs, and the context of the identifiedresources within the Media Presentation. Details of the MPD will bedescribed below.

In app-based enhancement signaling in ROUTE-based delivery, app-basedenhancement signaling pertains to the delivery of app-based enhancementcomponents, such as an application logic file, locally-cached mediafiles, an network content items, or a notification stream. Anapplication can also retrieve locally-cached data over a broadbandconnection when available.

Hereinafter, a description will be given of details of USBD/USDillustrated in the figure.

The top level or entry point SLS fragment is the USBD fragment. Anillustrated USBD fragment is an example of the present invention, basicfields of the USBD fragment not illustrated in the figure may beadditionally provided according to a given embodiment. As described inthe foregoing, the illustrated USBD fragment has an extended form, andmay have fields added to a basic configuration.

The illustrated USBD may have a bundleDescription root element. ThebundleDescription root element may have a userServiceDescriptionelement. The userServiceDescription element may correspond to aninstance for one service.

The userServiceDescription element may include @serviceId,@atsc:serviceId, @atsc:serviceStatus, @atsc:fullMPDUri, @atsc:sTSIDUri,name, serviceLanguage, atsc:capabilityCode and/or deliveryMethod.

@serviceId can be a globally unique URI that identifies a service,unique within the scope of the BSID. This parameter can be used to linkto ESG data (Service@globalServiceID).

@atsc:serviceId is a reference to corresponding service entry inLLS(SLT). The value of this attribute is the same value of serviceIdassigned to the entry.

@atsc:serviceStatus can specify the status of this service. The valueindicates whether this service is active or inactive. When set to “1”(true), that indicates service is active. When this field is not used,@atsc:serviceStatus may be set to a default value of 1.

@atsc:fullMPDUri can reference an MPD fragment which containsdescriptions for contents components of the service delivered overbroadcast and optionally, also over broadband.

@atsc:sTSIDUri can reference the S-TSID fragment which provides accessrelated parameters to the Transport sessions carrying contents of thisservice.

name can indicate name of the service as given by the lang attribute.name element can include lang attribute, which indicating language ofthe service name. The language can be specified according to XML datatypes.

serviceLanguage can represent available languages of the service. Thelanguage can be specified according to XML data types.

atsc:capabilityCode can specify the capabilities required in thereceiver to be able to create a meaningful presentation of the contentof this service. According to a given embodiment, this field may specifya predefined capability group. Here, the capability group may be a groupof capability attribute values for significant presentation. This fieldmay be omitted according to a given embodiment.

deliveryMethod can be a container of transport related informationpertaining to the contents of the service over broadcast and(optionally) broadband modes of access. Referring to data included inthe service, when the number of the data is N, delivery schemes forrespective data may be described by this element. The deliveryMethod mayinclude an r12:broadcastAppService element and an r12:unicastAppServiceelement. Each lower element may include a basePattern element as a lowerelement.

r12:broadcastAppService can be a DASH Representation delivered overbroadcast, in multiplexed or non-multiplexed form, containing thecorresponding media component(s) belonging to the service, across allPeriods of the affiliated media presentation. In other words, each ofthe fields may indicate DASH representation delivered through thebroadcast network.

r12:unicastAppService can be a DASH Representation delivered overbroadband, in multiplexed or non-multiplexed form, containing theconstituent media content component(s) belonging to the service, acrossall periods of the affiliated media presentation. In other words, eachof the fields may indicate DASH representation delivered via broadband.

basePattern can be a character pattern for use by the receiver to matchagainst any portion of the segment URL used by the DASH client torequest media segments of a parent representation under its containingperiod. A match implies that the corresponding requested media segmentis carried over broadcast transport. In a URL address for receiving DASHrepresentation expressed by each of the r12:broadcastAppService elementand the r12:unicastAppService element, a part of the URL, etc. may havea particular pattern. The pattern may be described by this field. Somedata may be distinguished using this information. The proposed defaultvalues may vary depending on embodiments. The “use” column illustratedin the figure relates to each field. Here, M may denote an essentialfield, O may denote an optional field, OD may denote an optional fieldhaving a default value, and CM may denote a conditional essential field.0 . . . 1 to 0 . . . N may indicate the number of available fields.

FIG. 6 illustrates an S-TSID fragment for ROUTE/DASH according to anembodiment of the present invention.

Hereinafter, a description will be given of the S-TSID illustrated inthe figure in detail.

S-TSID can be an SLS XML fragment which provides the overall sessiondescription information for transport session(s) which carry the contentcomponents of a service. The S-TSID is the SLS metadata fragment thatcontains the overall transport session description information for thezero or more ROUTE sessions and constituent LCT sessions in which themedia content components of a service are delivered. The S-TSID alsoincludes file metadata for the delivery object or object flow carried inthe LCT sessions of the service, as well as additional information onthe payload formats and content components carried in those LCTsessions.

Each instance of the S-TSID fragment is referenced in the USBD fragmentby the @atsc:sTSIDUri attribute of the userServiceDescription element.The illustrated S-TSID according to the present embodiment is expressedas an XML document. According to a given embodiment, the S-TSID may beexpressed in a binary format or as an XML document.

The illustrated S-TSID may have an S-TSID root element. The S-TSID rootelement may include @serviceId and/or RS.

@serviceID can be a reference corresponding service element in the USD.The value of this attribute can reference a service with a correspondingvalue of service_id.

The RS element may have information about a ROUTE session for deliveringthe service data. Service data or service components may be deliveredthrough a plurality of ROUTE sessions, and thus the number of RSelements may be 1 to N.

The RS element may include @bsid, @slpAddr, @dlpAddr, @dport, @PLPIDand/or LS.

@bsid can be an identifier of the broadcast stream within which thecontent component(s) of the broadcastAppService are carried. When thisattribute is absent, the default broadcast stream is the one whose PLPscarry SLS fragments for this service. Its value can be identical to thatof the broadcast_stream_id in the SLT.

@slpAddr can indicate source IP address. Here, the source IP address maybe a source IP address of a ROUTE session for delivering a servicecomponent included in the service. As described in the foregoing,service components of one service may be delivered through a pluralityof ROUTE sessions. Thus, the service components may be transmitted usinganother ROUTE session other than the ROUTE session for delivering theS-TSID. Therefore, this field may be used to indicate the source IPaddress of the ROUTE session. A default value of this field may be asource IP address of a current ROUTE session. When a service componentis delivered through another ROUTE session, and thus the ROUTE sessionneeds to be indicated, a value of this field may be a value of a sourceIP address of the ROUTE session. In this case, this field may correspondto M, that is, an essential field.

@dIpAddr can indicate destination IP address. Here, a destination IPaddress may be a destination IP address of a ROUTE session that deliversa service component included in a service. For a similar case to theabove description of @sIpAddr, this field may indicate a destination IPaddress of a ROUTE session that delivers a service component. A defaultvalue of this field may be a destination IP address of a current ROUTEsession. When a service component is delivered through another ROUTEsession, and thus the ROUTE session needs to be indicated, a value ofthis field may be a value of a destination IP address of the ROUTEsession. In this case, this field may correspond to M, that is, anessential field.

@dport can indicate destination port. Here, a destination port may be adestination port of a ROUTE session that delivers a service componentincluded in a service. For a similar case to the above description of@sIpAddr, this field may indicate a destination port of a ROUTE sessionthat delivers a service component. A default value of this field may bea destination port number of a current ROUTE session. When a servicecomponent is delivered through another ROUTE session, and thus the ROUTEsession needs to be indicated, a value of this field may be adestination port number value of the ROUTE session. In this case, thisfield may correspond to M, that is, an essential field.

@PLPID may be an ID of a PLP for a ROUTE session expressed by an RS. Adefault value may be an ID of a PLP of an LCT session including acurrent S-TSID. According to a given embodiment, this field may have anID value of a PLP for an LCT session for delivering an S-TSID in theROUTE session, and may have ID values of all PLPs for the ROUTE session.

An LS element may have information about an LCT session for delivering aservice data. Service data or service components may be deliveredthrough a plurality of LCT sessions, and thus the number of LS elementsmay be 1 to N.

The LS element may include @tsi, @PLPID, @bw, @startTime, @endTime,SrcFlow and/or RprFlow.

@tsi may indicate a TSI value of an LCT session for delivering a servicecomponent of a service.

@PLPID may have ID information of a PLP for the LCT session. This valuemay be overwritten on a basic ROUTE session value.

@bw may indicate a maximum bandwidth value. @startTime may indicate astart time of the LCT session. @endTime may indicate an end time of theLCT session. A SrcFlow element may describe a source flow of ROUTE. ARprFlow element may describe a repair flow of ROUTE.

The proposed default values may be varied according to an embodiment.The “use” column illustrated in the figure relates to each field. Here,M may denote an essential field, O may denote an optional field, OD maydenote an optional field having a default value, and CM may denote aconditional essential field. 0 . . . 1 to 0 . . . N may indicate thenumber of available fields.

Hereinafter, a description will be given of MPD for ROUTE/DASH.

The MPD is an SLS metadata fragment which contains a formalizeddescription of a DASH Media Presentation, corresponding to a linearservice of a given duration defined by the broadcaster (for example asingle TV program, or the set of contiguous linear TV programs over aperiod of time). The contents of the MPD provide the resourceidentifiers for Segments and the context for the identified resourceswithin the Media Presentation. The data structure and semantics of theMPD fragment can be according to the MPD defined by MPEG DASH.

One or more of the DASH Representations conveyed in the MPD can becarried over broadcast. The MPD may describe additional Representationsdelivered over broadband, e.g. in the case of a hybrid service, or tosupport service continuity in handoff from broadcast to broadcast due tobroadcast signal degradation (e.g. driving through a tunnel).

FIG. 7 illustrates a USBD/USD fragment for MMT according to anembodiment of the present invention.

MMT SLS for linear services comprises the USBD fragment and the MMTPackage (MP) table. The MP table is as described above. The USBDfragment contains service identification, device capabilitiesinformation, references to other SLS information required to access theservice and constituent media components, and the metadata to enable thereceiver to determine the transport mode (broadcast and/or broadband) ofthe service components. The MP table for MPU components, referenced bythe USBD, provides transport session descriptions for the MMTP sessionsin which the media content components of a service are delivered and thedescriptions of the Assets carried in those MMTP sessions.

The streaming content signaling component of the SLS for MPU componentscorresponds to the MP table defined in MMT. The MP table provides a listof MMT assets where each asset corresponds to a single service componentand the description of the location information for this component.

USBD fragments may also contain references to the S-TSID and the MPD asdescribed above, for service components delivered by the ROUTE protocoland the broadband, respectively. According to a given embodiment, indelivery through MMT, a service component delivered through the ROUTEprotocol is NRT data, etc. Thus, in this case, MPD may be unnecessary.In addition, in delivery through MMT, information about an LCT sessionfor delivering a service component, which is delivered via broadband, isunnecessary, and thus an S-TSID may be unnecessary. Here, an MMT packagemay be a logical collection of media data delivered using MMT. Here, anMMTP packet may refer to a formatted unit of media data delivered usingMMT. An MPU may refer to a generic container of independently decodabletimed/non-timed data. Here, data in the MPU is media codec agnostic.

Hereinafter, a description will be given of details of the USBD/USDillustrated in the figure.

The illustrated USBD fragment is an example of the present invention,and basic fields of the USBD fragment may be additionally providedaccording to an embodiment. As described in the foregoing, theillustrated USBD fragment has an extended form, and may have fieldsadded to a basic structure.

The illustrated USBD according to an embodiment of the present inventionis expressed as an XML document. According to a given embodiment, theUSBD may be expressed in a binary format or as an XML document.

The illustrated USBD may have a bundleDescription root element. ThebundleDescription root element may have a userServiceDescriptionelement. The userServiceDescription element may be an instance for oneservice.

The userServiceDescription element may include @serviceId,@atsc:serviceId, name, serviceLanguage, atsc:capabilityCode,atsc:Channel, atsc:mpuComponent, atsc:routeComponent,atsc:broadbandComponent and/or atsc:ComponentInfo.

Here, @serviceId, @atsc:serviceId, name, serviceLanguage, andatsc:capabilityCode may be as described above. The lang field below thename field may be as described above. atsc:capabilityCode may be omittedaccording to a given embodiment.

The userServiceDescription element may further include anatsc:contentAdvisoryRating element according to an embodiment. Thiselement may be an optional element. atsc:contentAdvisoryRating canspecify the content advisory rating. This field is not illustrated inthe figure.

atsc:Channel may have information about a channel of a service. Theatsc:Channel element may include @atsc:majorChannelNo,@atsc:minorChannelNo, @atsc:serviceLang, @atsc:serviceGenre,@atsc:serviceIcon and/or atsc:ServiceDescription. @atsc:majorChannelNo,@atsc:minorChannelNo, and @atsc:serviceLang may be omitted according toa given embodiment.

@atsc:majorChannelNo is an attribute that indicates the major channelnumber of the service.

@atsc:minorChannelNo is an attribute that indicates the minor channelnumber of the service.

@atsc:serviceLang is an attribute that indicates the primary languageused in the service.

@atsc:serviceGenre is an attribute that indicates primary genre of theservice.

@atsc:serviceIcon is an attribute that indicates the Uniform ResourceLocator (URL) for the icon used to represent this service.

atsc:ServiceDescription includes service description, possibly inmultiple languages. atsc:ServiceDescription includes can include@atsc:serviceDescrText and/or @atsc:serviceDescrLang.

@atsc:serviceDescrText is an attribute that indicates description of theservice.

@atsc:serviceDescrLang is an attribute that indicates the language ofthe serviceDescrText attribute above.

atsc:mpuComponent may have information about a content component of aservice delivered in a form of an MPU. atsc:mpuComponent may include@atsc:mmtPackageId and/or @atsc:nextMmtPackageId.

@atsc:mmtPackageId can reference a MMT Package for content components ofthe service delivered as MPUs.

@atsc:nextMmtPackageId can reference a MMT Package to be used after theone referenced by @atsc:mmtPackageId in time for content components ofthe service delivered as MPUs.

atsc:routeComponent may have information about a content component of aservice delivered through ROUTE. atsc:routeComponent may include@atsc:sTSIDUri, @sTSIDPlpId, @ sTSIDDestinationIpAddress,@sTSIDDestinationUdpPort, @sTSIDSourceIpAddress,@sTSIDMajorProtocolVersion and/or @sTSIDMinorProtocolVersion.

@atsc:sTSIDUri can be a reference to the S-TSID fragment which providesaccess related parameters to the Transport sessions carrying contents ofthis service. This field may be the same as a URI for referring to anS-TSID in USBD for ROUTE described above. As described in the foregoing,in service delivery by the MMTP, service components, which are deliveredthrough NRT, etc., may be delivered by ROUTE. This field may be used torefer to the S-TSID therefor.

@sTSIDPlpId can be a string representing an integer number indicatingthe PLP ID of the physical layer pipe carrying the S-TSID for thisservice. (default: current physical layer pipe).

@sTSIDDestinationIpAddress can be a string containing the dotted-IPv4destination address of the packets carrying S-TSID for this service.(default: current MMTP session's source IP address)

@sTSIDDestinationUdpPort can be a string containing the port number ofthe packets carrying S-TSID for this service.

@sTSIDSourceIpAddress can be a string containing the dotted-IPv4 sourceaddress of the packets carrying S-TSID for this service.

@sTSIDMajorProtocolVersion can indicate major version number of theprotocol used to deliver the S-TSID for this service. Default value is1.

@sTSIDMinorProtocolVersion can indicate minor version number of theprotocol used to deliver the S-TSID for this service. Default value is0.

atsc:broadbandComponent may have information about a content componentof a service delivered via broadband. In other words,atsc:broadbandComponent may be a field on the assumption of hybriddelivery. atsc:broadbandComponent may further include @atsc:fullfMPDUri.

@atsc:fullfMPDUri can be a reference to an MPD fragment which containsdescriptions for contents components of the service delivered overbroadband.

An atsc:ComponentInfo field may have information about an availablecomponent of a service. The atsc:ComponentInfo field may haveinformation about a type, a role, a name, etc. of each component. Thenumber of atsc:ComponentInfo fields may correspond to the number (N) ofrespective components. The atsc:ComponentInfo field may include@atsc:componentType, @atsc:componentRole, @atsc:componentProtectedFlag,@atsc:componentId and/or @atsc:componentName.

@atsc:componentType is an attribute that indicates the type of thiscomponent. Value of 0 indicates an audio component. Value of 1 indicatesa video component. Value of 2 indicated a closed caption component.Value of 3 indicates an application component. Values 4 to 7 arereserved. A meaning of a value of this field may be differently setdepending on embodiments.

@atsc:componentRole is an attribute that indicates the role or kind ofthis component.

For audio (when componentType attribute above is equal to 0): values ofcomponentRole attribute are as follows: 0=Complete main, 1=Music andEffects, 2=Dialog, 3=Commentary, 4=Visually Impaired, 5=HearingImpaired, 6=Voice-Over, 7-254=reserved, 255=unknown.

For video (when componentType attribute above is equal to 1) values ofcomponentRole attribute are as follows: 0=Primary video, 1=Alternativecamera view, 2=Other alternative video component, 3=Sign language inset,4=Follow subject video, 5=3D video left view, 6=3D video right view,7=3D video depth information, 8=Part of video array <x,y> of <n,m>,9=Follow-Subject metadata, 10-254=reserved, 255=unknown.

For Closed Caption component (when componentType attribute above isequal to 2) values of componentRole attribute are as follows: 0=Normal,1=Easy reader, 2-254=reserved, 255=unknown.

When componentType attribute above is between 3 to 7, inclusive, thecomponentRole can be equal to 255. A meaning of a value of this fieldmay be differently set depending on embodiments.

@atsc:componentProtectedFlag is an attribute that indicates if thiscomponent is protected (e.g. encrypted). When this flag is set to avalue of 1 this component is protected (e.g. encrypted). When this flagis set to a value of 0 this component is not protected (e.g. encrypted).When not present the value of componentProtectedFlag attribute isinferred to be equal to 0. A meaning of a value of this field may bedifferently set depending on embodiments.

@atsc:componentId is an attribute that indicates the identifier of thiscomponent. The value of this attribute can be the same as the asset_idin the MP table corresponding to this component.

@atsc:componentName is an attribute that indicates the human readablename of this component.

The proposed default values may vary depending on embodiments. The “use”column illustrated in the figure relates to each field. Here, M maydenote an essential field, O may denote an optional field, OD may denotean optional field having a default value, and CM may denote aconditional essential field. 0 . . . 1 to 0 . . . N may indicate thenumber of available fields.

Hereinafter, a description will be given of MPD for MMT.

The Media Presentation Description is an SLS metadata fragmentcorresponding to a linear service of a given duration defined by thebroadcaster (for example a single TV program, or the set of contiguouslinear TV programs over a period of time). The contents of the MPDprovide the resource identifiers for segments and the context for theidentified resources within the media presentation. The data structureand semantics of the MPD can be according to the MPD defined by MPEGDASH.

In the present embodiment, an MPD delivered by an MMTP session describesRepresentations delivered over broadband, e.g. in the case of a hybridservice, or to support service continuity in handoff from broadcast tobroadband due to broadcast signal degradation (e.g. driving under amountain or through a tunnel).

Hereinafter, a description will be given of an MMT signaling message forMMT.

When MMTP sessions are used to carry a streaming service, MMT signalingmessages defined by MMT are delivered by MMTP packets according tosignaling message mode defined by MMT. The value of the packet_id fieldof MMTP packets carrying service layer signaling is set to ‘00’ exceptfor MMTP packets carrying MMT signaling messages specific to an asset,which can be set to the same packet_id value as the MMTP packetscarrying the asset. Identifiers referencing the appropriate package foreach service are signaled by the USBD fragment as described above. MMTPackage Table (MPT) messages with matching MMT_package_id can bedelivered on the MMTP session signaled in the SLT. Each MMTP sessioncarries MMT signaling messages specific to its session or each assetdelivered by the MMTP session.

In other words, it is possible to access USBD of the MMTP session byspecifying an IP destination address/port number, etc. of a packethaving the SLS for a particular service in the SLT. As described in theforegoing, a packet ID of an MMTP packet carrying the SLS may bedesignated as a particular value such as 00, etc. It is possible toaccess an MPT message having a matched packet ID using theabove-described package IP information of USBD. As described below, theMPT message may be used to access each service component/asset.

The following MMTP messages can be delivered by the MMTP sessionsignaled in the SLT.

MMT Package Table (MPT) message: This message carries an MP (MMTPackage) table which contains the list of all Assets and their locationinformation as defined by MMT. If an Asset is delivered by a PLPdifferent from the current PLP delivering the MP table, the identifierof the PLP carrying the asset can be provided in the MP table usingphysical layer pipe identifier descriptor. The physical layer pipeidentifier descriptor will be described below.

MMT ATSC3 (MA3) message mmt_atsc3_message( ): This message carriessystem metadata specific for services including service layer signalingas described above. mmt_atsc3_message( ) will be described below.

The following MMTP messages can be delivered by the MMTP sessionsignaled in the SLT, if required.

Media Presentation Information (MPI) message: This message carries anMPI table which contains the whole document or a subset of a document ofpresentation information. An MP table associated with the MPI table alsocan be delivered by this message.

Clock Relation Information (CRI) message: This message carries a CRItable which contains clock related information for the mapping betweenthe NTP timestamp and the MPEG-2 STC. According to a given embodiment,the CRI message may not be delivered through the MMTP session.

The following MMTP messages can be delivered by each MMTP sessioncarrying streaming content.

Hypothetical Receiver Buffer Model message: This message carriesinformation required by the receiver to manage its buffer.

Hypothetical Receiver Buffer Model Removal message: This message carriesinformation required by the receiver to manage its MMT de-capsulationbuffer.

Hereinafter, a description will be given of mmt_atsc3_message( )corresponding to one of MMT signaling messages. An MMT Signaling messagemmt_atsc3_message( ) is defined to deliver information specific toservices according to the present invention described above. Thesignaling message may include message ID, version, and/or length fieldscorresponding to basic fields of the MMT signaling message. A payload ofthe signaling message may include service ID information, content typeinformation, content version information, content compressioninformation and/or URI information. The content type information mayindicate a type of data included in the payload of the signalingmessage. The content version information may indicate a version of dataincluded in the payload, and the content compression information mayindicate a type of compression applied to the data. The URI informationmay have URI information related to content delivered by the message.

Hereinafter, a description will be given of the physical layer pipeidentifier descriptor.

The physical layer pipe identifier descriptor is a descriptor that canbe used as one of descriptors of the MP table described above. Thephysical layer pipe identifier descriptor provides information about thePLP carrying an asset. If an asset is delivered by a PLP different fromthe current PLP delivering the MP table, the physical layer pipeidentifier descriptor can be used as an asset descriptor in theassociated MP table to identify the PLP carrying the asset. The physicallayer pipe identifier descriptor may further include BSID information inaddition to PLP ID information. The BSID may be an ID of a broadcaststream that delivers an MMTP packet for an asset described by thedescriptor.

FIG. 8 illustrates a link layer protocol architecture according to anembodiment of the present invention.

Hereinafter, a link layer will be described.

The link layer is the layer between the physical layer and the networklayer, and transports the data from the network layer to the physicallayer at the sending side and transports the data from the physicallayer to the network layer at the receiving side. The purpose of thelink layer includes abstracting all input packet types into a singleformat for processing by the physical layer, ensuring flexibility andfuture extensibility for as yet undefined input types. In addition,processing within the link layer ensures that the input data can betransmitted in an efficient manner, for example by providing options tocompress redundant information in the headers of input packets. Theoperations of encapsulation, compression and so on are referred to asthe link layer protocol and packets created using this protocol arecalled link layer packets. The link layer may perform functions such aspacket encapsulation, overhead reduction and/or signaling transmission,etc.

Hereinafter, packet encapsulation will be described. Link layer protocolallows encapsulation of any type of packet, including ones such as IPpackets and MPEG-2 TS. Using link layer protocol, the physical layerneed only process one single packet format, independent of the networklayer protocol type (here we consider MPEG-2 TS packet as a kind ofnetwork layer packet.) Each network layer packet or input packet istransformed into the payload of a generic link layer packet.Additionally, concatenation and segmentation can be performed in orderto use the physical layer resources efficiently when the input packetsizes are particularly small or large.

As described in the foregoing, segmentation may be used in packetencapsulation. When the network layer packet is too large to processeasily in the physical layer, the network layer packet is divided intotwo or more segments. The link layer packet header includes protocolfields to perform segmentation on the sending side and reassembly on thereceiving side. When the network layer packet is segmented, each segmentcan be encapsulated to link layer packet in the same order as originalposition in the network layer packet. Also each link layer packet whichincludes a segment of network layer packet can be transported to PHYlayer consequently.

As described in the foregoing, concatenation may be used in packetencapsulation. When the network layer packet is small enough for thepayload of a link layer packet to include several network layer packets,the link layer packet header includes protocol fields to performconcatenation. The concatenation is combining of multiple small sizednetwork layer packets into one payload. When the network layer packetsare concatenated, each network layer packet can be concatenated topayload of link layer packet in the same order as original input order.Also each packet which constructs a payload of link layer packet can bewhole packet, not a segment of packet.

Hereinafter, overhead reduction will be described. Use of the link layerprotocol can result in significant reduction in overhead for transportof data on the physical layer. The link layer protocol according to thepresent invention may provide IP overhead reduction and/or MPEG-2 TSoverhead reduction. In IP overhead reduction, IP packets have a fixedheader format, however some of the information which is needed in acommunication environment may be redundant in a broadcast environment.Link layer protocol provides mechanisms to reduce the broadcast overheadby compressing headers of IP packets. In MPEG-2 TS overhead reduction,link layer protocol provides sync byte removal, null packet deletionand/or common header removal (compression). First, sync byte removalprovides an overhead reduction of one byte per TS packet, secondly anull packet deletion mechanism removes the 188 byte null TS packets in amanner that they can be re-inserted at the receiver and finally a commonheader removal mechanism.

For signaling transmission, in the link layer protocol, a particularformat for the signaling packet may be provided for link layersignaling, which will be described below.

In the illustrated link layer protocol architecture according to anembodiment of the present invention, link layer protocol takes as inputnetwork layer packets such as IPv4, MPEG-2 TS and so on as inputpackets. Future extension indicates other packet types and protocolwhich is also possible to be input in link layer. Link layer protocolalso specifies the format and signaling for any link layer signaling,including information about mapping to specific channel to the physicallayer. Figure also shows how ALP incorporates mechanisms to improve theefficiency of transmission, via various header compression and deletionalgorithms. In addition, the link layer protocol may basicallyencapsulate input packets.

FIG. 9 illustrates a structure of a base header of a link layer packetaccording to an embodiment of the present invention. Hereinafter, thestructure of the header will be described.

A link layer packet can include a header followed by the data payload.The header of a link layer packet can include a base header, and mayinclude an additional header depending on the control fields of the baseheader. The presence of an optional header is indicated from flag fieldsof the additional header. According to a given embodiment, a fieldindicating the presence of an additional header and an optional headermay be positioned in the base header.

Hereinafter, the structure of the base header will be described. Thebase header for link layer packet encapsulation has a hierarchicalstructure. The base header can be two bytes in length and is the minimumlength of the link layer packet header.

The illustrated base header according to the present embodiment mayinclude a Packet_Type field, a PC field and/or a length field. Accordingto a given embodiment, the base header may further include an HM fieldor an S/C field.

Packet_Type field can be a 3-bit field that indicates the originalprotocol or packet type of the input data before encapsulation into alink layer packet. An IPv4 packet, a compressed IP packet, a link layersignaling packet, and other types of packets may have the base headerstructure and may be encapsulated. However, according to a givenembodiment, the MPEG-2 TS packet may have a different particularstructure, and may be encapsulated. When the value of Packet_Type is“000”, “001” “100” or “111”, that is the original data type of an ALPpacket is one of an IPv4 packet, a compressed IP packet, link layersignaling or extension packet. When the MPEG-2 TS packet isencapsulated, the value of Packet_Type can be “010”. Other values of thePacket_Type field may be reserved for future use.

Payload_Configuration (PC) field can be a 1-bit field that indicates theconfiguration of the payload. A value of 0 can indicate that the linklayer packet carries a single, whole input packet and the followingfield is the Header_Mode field. A value of 1 can indicate that the linklayer packet carries more than one input packet (concatenation) or apart of a large input packet (segmentation) and the following field isthe Segmentation_Concatenation field.

Header_Mode (HM) field can be a 1-bit field, when set to 0, that canindicate there is no additional header, and that the length of thepayload of the link layer packet is less than 2048 bytes. This value maybe varied depending on embodiments. A value of 1 can indicate that anadditional header for single packet defined below is present followingthe Length field. In this case, the length of the payload is larger than2047 bytes and/or optional features can be used (sub streamidentification, header extension, etc.). This value may be varieddepending on embodiments. This field can be present only whenPayload_Configuration field of the link layer packet has a value of 0.

Segmentation_Concatenation (S/C) field can be a 1-bit field, when set to0, that can indicate that the payload carries a segment of an inputpacket and an additional header for segmentation defined below ispresent following the Length field. A value of 1 can indicate that thepayload carries more than one complete input packet and an additionalheader for concatenation defined below is present following the Lengthfield. This field can be present only when the value ofPayload_Configuration field of the ALP packet is 1.

Length field can be a 11-bit field that indicates the 11 leastsignificant bits (LSBs) of the length in bytes of payload carried by thelink layer packet. When there is a Length_MSB field in the followingadditional header, the length field is concatenated with the Length_MSBfield, and is the LSB to provide the actual total length of the payload.The number of bits of the length field may be changed to another valuerather than 11 bits.

Following types of packet configuration are thus possible: a singlepacket without any additional header, a single packet with an additionalheader, a segmented packet and a concatenated packet. According to agiven embodiment, more packet configurations may be made through acombination of each additional header, an optional header, an additionalheader for signaling information to be described below, and anadditional header for time extension.

FIG. 10 illustrates a structure of an additional header of a link layerpacket according to an embodiment of the present invention.

Various types of additional headers may be present. Hereinafter, adescription will be given of an additional header for a single packet.

This additional header for single packet can be present when Header_Mode(HM)=“1”. The Header_Mode (HM) can be set to 1 when the length of thepayload of the link layer packet is larger than 2047 bytes or when theoptional fields are used. The additional header for single packet isshown in Figure (tsib10010).

Length_MSB field can be a 5-bit field that can indicate the mostsignificant bits (MSBs) of the total payload length in bytes in thecurrent link layer packet, and is concatenated with the Length fieldcontaining the 11 least significant bits (LSBs) to obtain the totalpayload length. The maximum length of the payload that can be signaledis therefore 65535 bytes. The number of bits of the length field may bechanged to another value rather than 11 bits. In addition, the number ofbits of the Length_MSB field may be changed, and thus a maximumexpressible payload length may be changed. According to a givenembodiment, each length field may indicate a length of a whole linklayer packet rather than a payload.

SIF (Sub stream Identifier Flag) field can be a 1-bit field that canindicate whether the sub stream ID (SID) is present after the HEF fieldor not. When there is no SID in this link layer packet, SIF field can beset to 0. When there is a SID after HEF field in the link layer packet,SIF can be set to 1. The detail of SID is described below.

HEF (Header Extension Flag) field can be a 1-bit field that canindicate, when set to 1 additional header is present for futureextension. A value of 0 can indicate that this extension header is notpresent.

Hereinafter, a description will be given of an additional header whensegmentation is used.

This additional header (tsib10020) can be present whenSegmentation_Concatenation (S/C)=“0”. Segment_Sequence_Number can be a5-bit unsigned integer that can indicate the order of the correspondingsegment carried by the link layer packet. For the link layer packetwhich carries the first segment of an input packet, the value of thisfield can be set to 0x0. This field can be incremented by one with eachadditional segment belonging to the segmented input packet.

Last_Segment_Indicator (LSI) can be a 1-bit field that can indicate,when set to 1, that the segment in this payload is the last one of inputpacket. A value of 0, can indicate that it is not last segment.

SIF (Sub stream Identifier Flag) can be a 1-bit field that can indicatewhether the SID is present after the HEF field or not. When there is noSID in the link layer packet, SIF field can be set to 0. When there is aSID after the HEF field in the link layer packet, SIF can be set to 1.

HEF (Header Extension Flag) can be a This 1-bit field that can indicate,when set to 1, that the optional header extension is present after theadditional header for future extensions of the link layer header. Avalue of 0 can indicate that optional header extension is not present.

According to a given embodiment, a packet ID field may be additionallyprovided to indicate that each segment is generated from the same inputpacket. This field may be unnecessary and thus be omitted when segmentsare transmitted in order.

Hereinafter, a description will be given of an additional header whenconcatenation is used.

This additional header (tsib10030) can be present whenSegmentation_Concatenation (S/C)=“1”.

Length_MSB can be a 4-bit field that can indicate MSB bits of thepayload length in bytes in this link layer packet. The maximum length ofthe payload is 32767 bytes for concatenation. As described in theforegoing, a specific numeric value may be changed.

Count can be a field that can indicate the number of the packetsincluded in the link layer packet. The number of the packets included inthe link layer packet, 2 can be set to this field. So, its maximum valueof concatenated packets in a link layer packet is 9. A scheme in whichthe count field indicates the number may be varied depending onembodiments. That is, the numbers from 1 to 8 may be indicated.

HEF (Header Extension Flag) can be a 1-bit field that can indicate, whenset to 1 the optional header extension is present after the additionalheader for future extensions of the link layer header. A value of 0, canindicate extension header is not present.

Component_Length can be a 12-bit length field that can indicate thelength in byte of each packet. Component_Length fields are included inthe same order as the packets present in the payload except lastcomponent packet. The number of length field can be indicated by(Count+1). According to a given embodiment, length fields, the number ofwhich is the same as a value of the count field, may be present. When alink layer header consists of an odd number of Component_Length, fourstuffing bits can follow after the last Component_Length field. Thesebits can be set to 0. According to a given embodiment, aComponent_length field indicating a length of a last concatenated inputpacket may not be present. In this case, the length of the lastconcatenated input packet may correspond to a length obtained bysubtracting a sum of values indicated by respective Component_lengthfields from a whole payload length.

Hereinafter, the optional header will be described.

As described in the foregoing, the optional header may be added to arear of the additional header. The optional header field can contain SIDand/or header extension. The SID is used to filter out specific packetstream in the link layer level. One example of SID is the role ofservice identifier in a link layer stream carrying multiple services.The mapping information between a service and the SID valuecorresponding to the service can be provided in the SLT, if applicable.The header extension contains extended field for future use. Receiverscan ignore any header extensions which they do not understand.

SID (Sub stream Identifier) can be a 8-bit field that can indicate thesub stream identifier for the link layer packet. If there is optionalheader extension, SID present between additional header and optionalheader extension.

Header_Extension ( ) can include the fields defined below.

Extension_Type can be an 8-bit field that can indicate the type of theHeader_Extension ( ).

Extension_Length can be a 8-bit field that can indicate the length ofthe Header Extension ( ) in bytes counting from the next byte to thelast byte of the Header_Extension ( ).

Extension_Byte can be a byte representing the value of theHeader_Extension ( ).

FIG. 11 illustrates a structure of an additional header of a link layerpacket according to another embodiment of the present invention.

Hereinafter, a description will be given of an additional header forsignaling information.

How link layer signaling is incorporated into link layer packets are asfollows.

Signaling packets are identified by when the Packet_Type field of thebase header is equal to 100.

Figure (tsib11010) shows the structure of the link layer packetscontaining additional header for signaling information. In addition tothe link layer header, the link layer packet can consist of twoadditional parts, additional header for signaling information and theactual signaling data itself. The total length of the link layersignaling packet is shown in the link layer packet header.

The additional header for signaling information can include followingfields. According to a given embodiment, some fields may be omitted.

Signaling_Type can be an 8-bit field that can indicate the type ofsignaling.

Signaling_Type_Extension can be a 16-bit filed that can indicate theattribute of the signaling. Detail of this field can be defined insignaling specification.

Signaling_Version can be an 8-bit field that can indicate the version ofsignaling.

Signaling_Format can be a 2-bit field that can indicate the data formatof the signaling data. Here, a signaling format may refer to a dataformat such as a binary format, an XML format, etc.

Signaling_Encoding can be a 2-bit field that can specify theencoding/compression format. This field may indicate whether compressionis not performed and which type of compression is performed.

Hereinafter, a description will be given of an additional header forpacket type extension.

In order to provide a mechanism to allow an almost unlimited number ofadditional protocol and packet types to be carried by link layer in thefuture, the additional header is defined. Packet type extension can beused when Packet_type is 111 in the base header as described above.Figure (tsib11020) shows the structure of the link layer packetscontaining additional header for type extension.

The additional header for type extension can include following fields.According to a given embodiment, some fields may be omitted.

extended_type can be a 16-bit field that can indicate the protocol orpacket type of the input encapsulated in the link layer packet aspayload. This field cannot be used for any protocol or packet typealready defined by Packet_Type field.

FIG. 12 illustrates a header structure of a link layer packet for anMPEG-2 TS packet and an encapsulation process thereof according to anembodiment of the present invention.

Hereinafter, a description will be given of a format of the link layerpacket when the MPEG-2 TS packet is input as an input packet.

In this case, the Packet_Type field of the base header is equal to 010.Multiple TS packets can be encapsulated within each link layer packet.The number of TS packets is signaled via the NUMTS field. In this case,as described in the foregoing, a particular link layer packet headerformat may be used.

Link layer provides overhead reduction mechanisms for MPEG-2 TS toenhance the transmission efficiency. The sync byte (0x47) of each TSpacket can be deleted. The option to delete NULL packets and similar TSheaders is also provided.

In order to avoid unnecessary transmission overhead, TS null packets(PID=0x1FFF) may be removed. Deleted null packets can be recovered inreceiver side using DNP field. The DNP field indicates the count ofdeleted null packets. Null packet deletion mechanism using DNP field isdescribed below.

In order to achieve more transmission efficiency, similar header ofMPEG-2 TS packets can be removed. When two or more successive TS packetshave sequentially increased continuity counter fields and other headerfields are the same, the header is sent once at the first packet and theother headers are deleted. HDM field can indicate whether the headerdeletion is performed or not. Detailed procedure of common TS headerdeletion is described below.

When all three overhead reduction mechanisms are performed, overheadreduction can be performed in sequence of sync removal, null packetdeletion, and common header deletion. According to a given embodiment, aperformance order of respective mechanisms may be changed. In addition,some mechanisms may be omitted according to a given embodiment.

The overall structure of the link layer packet header when using MPEG-2TS packet encapsulation is depicted in Figure (tsib12010).

Hereinafter, a description will be given of each illustrated field.Packet_Type can be a 3-bit field that can indicate the protocol type ofinput packet as describe above. For MPEG-2 TS packet encapsulation, thisfield can always be set to 010.

NUMTS (Number of TS packets) can be a 4-bit field that can indicate thenumber of TS packets in the payload of this link layer packet. A maximumof 16 TS packets can be supported in one link layer packet. The value ofNUMTS=0 can indicate that 16 TS packets are carried by the payload ofthe link layer packet. For all other values of NUMTS, the same number ofTS packets are recognized, e.g. NUMTS=0001 means one TS packet iscarried.

AHF (Additional Header Flag) can be a field that can indicate whetherthe additional header is present of not. A value of 0 indicates thatthere is no additional header. A value of 1 indicates that an additionalheader of length 1-byte is present following the base header. If null TSpackets are deleted or TS header compression is applied this field canbe set to 1. The additional header for TS packet encapsulation consistsof the following two fields and is present only when the value of AHF inthis link layer packet is set to 1.

HDM (Header Deletion Mode) can be a 1-bit field that indicates whetherTS header deletion can be applied to this link layer packet. A value of1 indicates that TS header deletion can be applied. A value of “0”indicates that the TS header deletion method is not applied to this linklayer packet.

DNP (Deleted Null Packets) can be a 7-bit field that indicates thenumber of deleted null TS packets prior to this link layer packet. Amaximum of 128 null TS packets can be deleted. When HDM=0 the value ofDNP=0 can indicate that 128 null packets are deleted. When HDM=1 thevalue of DNP=0 can indicate that no null packets are deleted. For allother values of DNP, the same number of null packets are recognized,e.g. DNP=5 means 5 null packets are deleted.

The number of bits of each field described above may be changed.According to the changed number of bits, a minimum/maximum value of avalue indicated by the field may be changed. These numbers may bechanged by a designer.

Hereinafter, SYNC byte removal will be described.

When encapsulating TS packets into the payload of a link layer packet,the SYNC byte (0x47) from the start of each TS packet can be deleted.Hence the length of the MPEG2-TS packet encapsulated in the payload ofthe link layer packet is always of length 187 bytes (instead of 188bytes originally).

Hereinafter, null packet deletion will be described.

Transport Stream rules require that bit rates at the output of atransmitter's multiplexer and at the input of the receiver'sde-multiplexer are constant in time and the end-to-end delay is alsoconstant. For some Transport Stream input signals, null packets may bepresent in order to accommodate variable bitrate services in a constantbitrate stream. In this case, in order to avoid unnecessary transmissionoverhead, TS null packets (that is TS packets with PID=0x1FFF) may beremoved. The process is carried-out in a way that the removed nullpackets can be re-inserted in the receiver in the exact place where theywere originally, thus guaranteeing constant bitrate and avoiding theneed for PCR time stamp updating.

Before generation of a link layer packet, a counter called DNP (DeletedNull-Packets) can first be reset to zero and then incremented for eachdeleted null packet preceding the first non-null TS packet to beencapsulated into the payload of the current link layer packet. Then agroup of consecutive useful TS packets is encapsulated into the payloadof the current link layer packet and the value of each field in itsheader can be determined. After the generated link layer packet isinjected to the physical layer, the DNP is reset to zero. When DNPreaches its maximum allowed value, if the next packet is also a nullpacket, this null packet is kept as a useful packet and encapsulatedinto the payload of the next link layer packet. Each link layer packetcan contain at least one useful TS packet in its payload.

Hereinafter, TS packet header deletion will be described. TS packetheader deletion may be referred to as TS packet header compression.

When two or more successive TS packets have sequentially increasedcontinuity counter fields and other header fields are the same, theheader is sent once at the first packet and the other headers aredeleted. When the duplicated MPEG-2 TS packets are included in two ormore successive TS packets, header deletion cannot be applied intransmitter side. HDM field can indicate whether the header deletion isperformed or not. When TS header deletion is performed, HDM can be setto 1. In the receiver side, using the first packet header, the deletedpacket headers are recovered, and the continuity counter is restored byincreasing it in order from that of the first header.

An example tsib12020 illustrated in the figure is an example of aprocess in which an input stream of a TS packet is encapsulated into alink layer packet. First, a TS stream including TS packets having SYNCbyte (0x47) may be input. First, sync bytes may be deleted through async byte deletion process. In this example, it is presumed that nullpacket deletion is not performed.

Here, it is presumed that packet headers of eight TS packets have thesame field values except for CC, that is, a continuity counter fieldvalue. In this case, TS packet deletion/compression may be performed.Seven remaining TS packet headers are deleted except for a first TSpacket header corresponding to CC=1. The processed TS packets may beencapsulated into a payload of the link layer packet.

In a completed link layer packet, a Packet_Type field corresponds to acase in which TS packets are input, and thus may have a value of 010. ANUMTS field may indicate the number of encapsulated TS packets. An AHFfield may be set to 1 to indicate the presence of an additional headersince packet header deletion is performed. An HDM field may be set to 1since header deletion is performed. DNP may be set to 0 since nullpacket deletion is not performed.

FIG. 13 illustrates an example of adaptation modes in IP headercompression according to an embodiment of the present invention(transmitting side).

Hereinafter, IP header compression will be described.

In the link layer, IP header compression/decompression scheme can beprovided. IP header compression can include two parts: headercompressor/decompressor and adaptation module. The header compressionscheme can be based on the Robust Header Compression (RoHC). Inaddition, for broadcasting usage, adaptation function is added.

In the transmitter side, ROHC compressor reduces the size of header foreach packet. Then, adaptation module extracts context information andbuilds signaling information from each packet stream. In the receiverside, adaptation module parses the signaling information associated withthe received packet stream and attaches context information to thereceived packet stream. ROHC decompressor reconstructs the original IPpacket by recovering the packet header.

The header compression scheme can be based on the RoHC as describedabove. In particular, in the present system, an RoHC framework canoperate in a unidirectional mode (U mode) of the RoHC. In addition, inthe present system, it is possible to use an RoHC UDP header compressionprofile which is identified by a profile identifier of 0x0002.

Hereinafter, adaptation will be described.

In case of transmission through the unidirectional link, if a receiverhas no information of context, decompressor cannot recover the receivedpacket header until receiving full context. This may cause channelchange delay and turn on delay. For this reason, context information andconfiguration parameters between compressor and decompressor can bealways sent with packet flow.

The Adaptation function provides out-of-band transmission of theconfiguration parameters and context information. Out-of-bandtransmission can be done through the link layer signaling. Therefore,the adaptation function is used to reduce the channel change delay anddecompression error due to loss of context information.

Hereinafter, extraction of context information will be described.

Context information may be extracted using various schemes according toadaptation mode. In the present invention, three examples will bedescribed below. The scope of the present invention is not restricted tothe examples of the adaptation mode to be described below. Here, theadaptation mode may be referred to as a context extraction mode.

Adaptation Mode 1 (not illustrated) may be a mode in which no additionaloperation is applied to a basic RoHC packet stream. In other words, theadaptation module may operate as a buffer in this mode. Therefore, inthis mode, context information may not be included in link layersignaling

In Adaptation Mode 2 (tsib13010), the adaptation module can detect theIR packet from ROHC packet flow and extract the context information(static chain). After extracting the context information, each IR packetcan be converted to an IR-DYN packet. The converted IR-DYN packet can beincluded and transmitted inside the ROHC packet flow in the same orderas IR packet, replacing the original packet.

In Adaptation Mode 3 (tsib13020), the adaptation module can detect theIR and IR-DYN packet from ROHC packet flow and extract the contextinformation. The static chain and dynamic chain can be extracted from IRpacket and dynamic chain can be extracted from IR-DYN packet. Afterextracting the context information, each IR and IR-DYN packet can beconverted to a compressed packet. The compressed packet format can bethe same with the next packet of IR or IR-DYN packet. The convertedcompressed packet can be included and transmitted inside the ROHC packetflow in the same order as IR or IR-DYN packet, replacing the originalpacket.

Signaling (context) information can be encapsulated based ontransmission structure. For example, context information can beencapsulated to the link layer signaling. In this case, the packet typevalue can be set to “100”.

In the above-described Adaptation Modes 2 and 3, a link layer packet forcontext information may have a packet type field value of 100. Inaddition, a link layer packet for compressed IP packets may have apacket type field value of 001. The values indicate that each of thesignaling information and the compressed IP packets are included in thelink layer packet as described above.

Hereinafter, a description will be given of a method of transmitting theextracted context information.

The extracted context information can be transmitted separately fromROHC packet flow, with signaling data through specific physical datapath. The transmission of context depends on the configuration of thephysical layer path. The context information can be sent with other linklayer signaling through the signaling data pipe.

In other words, the link layer packet having the context information maybe transmitted through a signaling PLP together with link layer packetshaving other link layer signaling information (Packet_Type=100).Compressed IP packets from which context information is extracted may betransmitted through a general PLP (Packet_Type=001). Here, depending onembodiments, the signaling PLP may refer to an L1 signaling path. Inaddition, depending on embodiments, the signaling PLP may not beseparated from the general PLP, and may refer to a particular andgeneral PLP through which the signaling information is transmitted.

At a receiving side, prior to reception of a packet stream, a receivermay need to acquire signaling information. When receiver decodes initialPLP to acquire the signaling information, the context signaling can bealso received. After the signaling acquisition is done, the PLP toreceive packet stream can be selected. In other words, the receiver mayacquire the signaling information including the context information byselecting the initial PLP. Here, the initial PLP may be theabove-described signaling PLP. Thereafter, the receiver may select a PLPfor acquiring a packet stream. In this way, the context information maybe acquired prior to reception of the packet stream.

After the PLP for acquiring the packet stream is selected, theadaptation module can detect IR-DYN packet form received packet flow.Then, the adaptation module parses the static chain from the contextinformation in the signaling data. This is similar to receiving the IRpacket. For the same context identifier, IR-DYN packet can be recoveredto IR packet. Recovered ROHC packet flow can be sent to ROHCdecompressor. Thereafter, decompression may be started.

FIG. 14 illustrates a link mapping table (LMT) and an RoHC-U descriptiontable according to an embodiment of the present invention.

Hereinafter, link layer signaling will be described.

Generally, link layer signaling is operates under IP level. At thereceiver side, link layer signaling can be obtained earlier than IPlevel signaling such as Service List Table (SLT) and Service LayerSignaling (SLS). Therefore, link layer signaling can be obtained beforesession establishment.

For link layer signaling, there can be two kinds of signaling accordinginput path: internal link layer signaling and external link layersignaling. The internal link layer signaling is generated in link layerat transmitter side. And the link layer takes the signaling fromexternal module or protocol. This kind of signaling information isconsidered as external link layer signaling. If some signaling need tobe obtained prior to IP level signaling, external signaling istransmitted in format of link layer packet.

The link layer signaling can be encapsulated into link layer packet asdescribed above. The link layer packets can carry any format of linklayer signaling, including binary and XML. The same signalinginformation may not be transmitted in different formats for the linklayer signaling.

Internal link layer signaling may include signaling information for linkmapping. The Link Mapping Table (LMT) provides a list of upper layersessions carried in a PLP. The LMT also provides addition informationfor processing the link layer packets carrying the upper layer sessionsin the link layer.

An example of the LMT (tsib14010) according to the present invention isillustrated.

signaling_type can be an 8-bit unsigned integer field that indicates thetype of signaling carried by this table. The value of signaling_typefield for Link Mapping Table (LMT) can be set to 0x01.

PLP_ID can be an 8-bit field that indicates the PLP corresponding tothis table.

num_session can be an 8-bit unsigned integer field that provides thenumber of upper layer sessions carried in the PLP identified by theabove PLP_ID field. When the value of signaling_type field is 0x01, thisfield can indicate the number of UDP/IP sessions in the PLP.

src_IP_add can be a 32-bit unsigned integer field that contains thesource IP address of an upper layer session carried in the PLPidentified by the PLP_ID field.

dst_IP_add can be a 32-bit unsigned integer field that contains thedestination IP address of an upper layer session carried in the PLPidentified by the PLP_ID field.

src_UDP_port can be a 16-bit unsigned integer field that represents thesource UDP port number of an upper layer session carried in the PLPidentified by the PLP_ID field.

dst_UDP_port can be a 16-bit unsigned integer field that represents thedestination UDP port number of an upper layer session carried in the PLPidentified by the PLP_ID field.

SID_flag can be a 1-bit Boolean field that indicates whether the linklayer packet carrying the upper layer session identified by above 4fields, Src_IP_add, Dst_IP_add, Src_UDP_Port and Dst_UDP_Port, has anSID field in its optional header. When the value of this field is set to0, the link layer packet carrying the upper layer session may not havean SID field in its optional header. When the value of this field is setto 1, the link layer packet carrying the upper layer session can have anSID field in its optional header and the value the SID field can be sameas the following SID field in this table.

compressed_flag can be a 1-bit Boolean field that indicates whether theheader compression is applied the link layer packets carrying the upperlayer session identified by above 4 fields, Src_IP_add, Dst_IP_add,Src_UDP_Port and Dst_UDP_Port. When the value of this field is set to 0,the link layer packet carrying the upper layer session may have a valueof 0x00 of Packet_Type field in its base header. When the value of thisfield is set to 1, the link layer packet carrying the upper layersession may have a value of 0x01 of Packet_Type field in its base headerand the Context_ID field can be present.

SID can be an 8-bit unsigned integer field that indicates sub streamidentifier for the link layer packets carrying the upper layer sessionidentified by above 4 fields, Src_IP_add, Dst_IP_add, Src_UDP_Port andDst_UDP_Port. This field can be present when the value of SID_flag isequal to 1.

context_id can be an 8-bit field that provides a reference for thecontext id (CID) provided in the ROHC-U description table. This fieldcan be present when the value of compressed_flag is equal to 1.

An example of the RoHC-U description table (tsib14020) according to thepresent invention is illustrated. As described in the foregoing, theRoHC-U adaptation module may generate information related to headercompression.

signaling_type can be an 8-bit field that indicates the type ofsignaling carried by this table. The value of signaling_type field forROHC-U description table (RDT) can be set to “0x02”.

PLP_ID can be an 8-bit field that indicates the PLP corresponding tothis table.

context_id can be an 8-bit field that indicates the context id (CID) ofthe compressed IP stream. In this system, 8-bit CID can be used forlarge CID.

context_profile can be an 8-bit field that indicates the range ofprotocols used to compress the stream. This field can be omitted.

adaptation_mode can be a 2-bit field that indicates the mode ofadaptation module in this PLP. Adaptation modes have been describedabove.

context_config can be a 2-bit field that indicates the combination ofthe context information. If there is no context information in thistable, this field may be set to “0x0”. If the static_chain( ) ordynamic_chain( ) byte is included in this table, this field may be setto “0x01” or “0x02” respectively. If both of the static_chain( ) anddynamic_chain( ) byte are included in this table, this field may be setto “0x03”.

context_length can be an 8-bit field that indicates the length of thestatic chain byte sequence. This field can be omitted.

static_chain_byte ( ) can be a field that conveys the static informationused to initialize the ROHC-U decompressor. The size and structure ofthis field depend on the context profile.

dynamic_chain_byte ( ) can be a field that conveys the dynamicinformation used to initialize the ROHC-U decompressor. The size andstructure of this field depend on the context profile.

The static_chain_byte can be defined as sub-header information of IRpacket. The dynamic_chain_byte can be defined as sub-header informationof IR packet and IR-DYN packet.

FIG. 15 illustrates a structure of a link layer on a transmitter sideaccording to an embodiment of the present invention.

The present embodiment presumes that an IP packet is processed. From afunctional point of view, the link layer on the transmitter side maybroadly include a link layer signaling part in which signalinginformation is processed, an overhead reduction part, and/or anencapsulation part. In addition, the link layer on the transmitter sidemay include a scheduler for controlling and scheduling an overalloperation of the link layer and/or input and output parts of the linklayer.

First, signaling information of an upper layer and/or a system parametertsib15010 may be delivered to the link layer. In addition, an IP streamincluding IP packets may be delivered to the link layer from an IP layertsib15110.

As described above, the scheduler tsib15020 may determine and controloperations of several modules included in the link layer. The deliveredsignaling information and/or system parameter tsib15010 may be filtereror used by the scheduler tsib15020. Information, which corresponds to apart of the delivered signaling information and/or system parametertsib15010, necessary for a receiver may be delivered to the link layersignaling part. In addition, information, which corresponds to a part ofthe signaling information, necessary for an operation of the link layermay be delivered to an overhead reduction controller tsib15120 or anencapsulation controller tsib15180.

The link layer signaling part may collect information to be transmittedas a signal in a physical layer, and convert/configure the informationin a form suitable for transmission. The link layer signaling part mayinclude a signaling manager tsib15030, a signaling formatter tsib15040,and/or a buffer for channels tsib15050.

The signaling manager tsib15030 may receive signaling informationdelivered from the scheduler tsib15020 and/or signaling (and/or context)information delivered from the overhead reduction part. The signalingmanager tsib15030 may determine a path for transmission of the signalinginformation for delivered data. The signaling information may bedelivered through the path determined by the signaling managertsib15030. As described in the foregoing, signaling information to betransmitted through a divided channel such as the FIC, the EAS, etc. maybe delivered to the signaling formatter tsib15040, and other signalinginformation may be delivered to an encapsulation buffer tsib15070.

The signaling formatter tsib15040 may format related signalinginformation in a form suitable for each divided channel such thatsignaling information may be transmitted through a separately dividedchannel. As described in the foregoing, the physical layer may includeseparate physically/logically divided channels. The divided channels maybe used to transmit FIC signaling information or EAS-relatedinformation. The FIC or EAS-related information may be sorted by thesignaling manager tsib15030, and input to the signaling formattertsib15040. The signaling formatter tsib15040 may format the informationbased on each separate channel. When the physical layer is designed totransmit particular signaling information through a separately dividedchannel other than the FIC and the EAS, a signaling formatter for theparticular signaling information may be additionally provided. Throughthis scheme, the link layer may be compatible with various physicallayers.

The buffer for channels tsib15050 may deliver the signaling informationreceived from the signaling formatter tsib15040 to separate dedicatedchannels tsib15060. The number and content of the separate channels mayvary depending on embodiments.

As described in the foregoing, the signaling manager tsib15030 maydeliver signaling information, which is not delivered to a particularchannel, to the encapsulation buffer tsib15070. The encapsulation buffertsib15070 may function as a buffer that receives the signalinginformation which is not delivered to the particular channel.

An encapsulation block for signaling information tsib15080 mayencapsulate the signaling information which is not delivered to theparticular channel A transmission buffer tsib15090 may function as abuffer that delivers the encapsulated signaling information to a DP forsignaling information tsib15100. Here, the DP for signaling informationtsib15100 may refer to the above-described PLS region.

The overhead reduction part may allow efficient transmission by removingoverhead of packets delivered to the link layer. It is possible toconfigure overhead reduction parts corresponding to the number of IPstreams input to the link layer.

An overhead reduction buffer tsib15130 may receive an IP packetdelivered from an upper layer. The received IP packet may be input tothe overhead reduction part through the overhead reduction buffertsib15130.

An overhead reduction controller tsib15120 may determine whether toperform overhead reduction on a packet stream input to the overheadreduction buffer tsib15130. The overhead reduction controller tsib15120may determine whether to perform overhead reduction for each packetstream. When overhead reduction is performed on a packet stream, packetsmay be delivered to a robust header compression (RoHC) compressortsib15140 to perform overhead reduction. When overhead reduction is notperformed on a packet stream, packets may be delivered to theencapsulation part to perform encapsulation without overhead reduction.Whether to perform overhead reduction of packets may be determined basedon the signaling information tsib15010 delivered to the link layer. Thesignaling information may be delivered to the encapsulation controllertsib15180 by the scheduler tsib15020.

The RoHC compressor tsib15140 may perform overhead reduction on a packetstream. The RoHC compressor tsib15140 may perform an operation ofcompressing a header of a packet. Various schemes may be used foroverhead reduction. Overhead reduction may be performed using a schemeproposed by the present invention. The present invention presumes an IPstream, and thus an expression “RoHC compressor” is used. However, thename may be changed depending on embodiments. The operation is notrestricted to compression of the IP stream, and overhead reduction ofall types of packets may be performed by the RoHC compressor tsib15140.

A packet stream configuration block tsib15150 may separate informationto be transmitted to a signaling region and information to betransmitted to a packet stream from IP packets having compressedheaders. The information to be transmitted to the packet stream mayrefer to information to be transmitted to a DP region. The informationto be transmitted to the signaling region may be delivered to asignaling and/or context controller tsib15160. The information to betransmitted to the packet stream may be transmitted to the encapsulationpart.

The signaling and/or context controller tsib15160 may collect signalingand/or context information and deliver the signaling and/or contextinformation to the signaling manager in order to transmit the signalingand/or context information to the signaling region.

The encapsulation part may perform an operation of encapsulating packetsin a form suitable for a delivery to the physical layer. It is possibleto configure encapsulation parts corresponding to the number of IPstreams.

An encapsulation buffer tsib15170 may receive a packet stream forencapsulation. Packets subjected to overhead reduction may be receivedwhen overhead reduction is performed, and an input IP packet may bereceived without change when overhead reduction is not performed.

An encapsulation controller tsib15180 may determine whether toencapsulate an input packet stream. When encapsulation is performed, thepacket stream may be delivered to a segmentation/concatenation blocktsib15190. When encapsulation is not performed, the packet stream may bedelivered to a transmission buffer tsib15230. Whether to encapsulatepackets may be determined based on the signaling information tsib15010delivered to the link layer. The signaling information may be deliveredto the encapsulation controller tsib15180 by the scheduler tsib15020.

In the segmentation/concatenation block tsib15190, the above-describedsegmentation or concatenation operation may be performed on packets. Inother words, when an input IP packet is longer than a link layer packetcorresponding to an output of the link layer, one IP packet may besegmented into several segments to configure a plurality of link layerpacket payloads. On the other hand, when an input IP packet is shorterthan a link layer packet corresponding to an output of the link layer,several IP packets may be concatenated to configure one link layerpacket payload.

A packet configuration table tsib15200 may have configurationinformation of a segmented and/or concatenated link layer packet. Atransmitter and a receiver may have the same information in the packetconfiguration table tsib15200. The transmitter and the receiver mayrefer to the information of the packet configuration table tsib15200. Anindex value of the information of the packet configuration tabletsib15200 may be included in a header of the link layer packet.

A link layer header information block tsib15210 may collect headerinformation generated in an encapsulation process. In addition, the linklayer header information block tsib15210 may collect header informationincluded in the packet configuration table tsib15200. The link layerheader information block tsib15210 may configure header informationaccording to a header structure of the link layer packet.

A header attachment block tsib15220 may add a header to a payload of asegmented and/or concatenated link layer packet. The transmission buffertsib15230 may function as a buffer to deliver the link layer packet to aDP tsib15240 of the physical layer.

The respective blocks, modules, or parts may be configured as onemodule/protocol or a plurality of modules/protocols in the link layer.

FIG. 16 illustrates a structure of a link layer on a receiver sideaccording to an embodiment of the present invention.

The present embodiment presumes that an IP packet is processed. From afunctional point of view, the link layer on the receiver side maybroadly include a link layer signaling part in which signalinginformation is processed, an overhead processing part, and/or adecapsulation part. In addition, the link layer on the receiver side mayinclude a scheduler for controlling and scheduling overall operation ofthe link layer and/or input and output parts of the link layer.

First, information received through a physical layer may be delivered tothe link layer. The link layer may process the information, restore anoriginal state before being processed at a transmitter side, and thendeliver the information to an upper layer. In the present embodiment,the upper layer may be an IP layer.

Information, which is separated in the physical layer and deliveredthrough a particular channel tsib16030, may be delivered to a link layersignaling part. The link layer signaling part may determine signalinginformation received from the physical layer, and deliver the determinedsignaling information to each part of the link layer.

A buffer for channels tsib16040 may function as a buffer that receivessignaling information transmitted through particular channels. Asdescribed in the foregoing, when physically/logically divided separatechannels are present in the physical layer, it is possible to receivesignaling information transmitted through the channels. When theinformation received from the separate channels is segmented, thesegmented information may be stored until complete information isconfigured.

A signaling decoder/parser tsib16050 may verify a format of thesignaling information received through the particular channel, andextract information to be used in the link layer. When the signalinginformation received through the particular channel is encoded, decodingmay be performed. In addition, according to a given embodiment, it ispossible to verify integrity, etc. of the signaling information.

A signaling manager tsib16060 may integrate signaling informationreceived through several paths. Signaling information received through aDP for signaling tsib16070 to be described below may be integrated inthe signaling manager tsib16060. The signaling manager tsib16060 maydeliver signaling information necessary for each part in the link layer.For example, the signaling manager tsib16060 may deliver contextinformation, etc. for recovery of a packet to the overhead processingpart. In addition, the signaling manager tsib16060 may deliver signalinginformation for control to a scheduler tsib16020.

General signaling information, which is not received through a separateparticular channel, may be received through the DP for signalingtsib16070. Here, the DP for signaling may refer to PLS, L1, etc. Here,the DP may be referred to as a PLP. A reception buffer tsib16080 mayfunction as a buffer that receives signaling information delivered fromthe DP for signaling. In a decapsulation block for signaling informationtsib16090, the received signaling information may be decapsulated. Thedecapsulated signaling information may be delivered to the signalingmanager tsib16060 through a decapsulation buffer tsib16100. As describedin the foregoing, the signaling manager tsib16060 may collate signalinginformation, and deliver the collated signaling information to anecessary part in the link layer.

The scheduler tsib16020 may determine and control operations of severalmodules included in the link layer. The scheduler tsib16020 may controleach part of the link layer using receiver information tsib16010 and/orinformation delivered from the signaling manager tsib16060. In addition,the scheduler tsib16020 may determine an operation mode, etc. of eachpart. Here, the receiver information tsib16010 may refer to informationpreviously stored in the receiver. The scheduler tsib16020 may useinformation changed by a user such as channel switching, etc. to performa control operation.

The decapsulation part may filter a packet received from a DP tsib16110of the physical layer, and separate a packet according to a type of thepacket. It is possible to configure decapsulation parts corresponding tothe number of DPs that can be simultaneously decoded in the physicallayer.

The decapsulation buffer tsib16100 may function as a buffer thatreceives a packet stream from the physical layer to performdecapsulation. A decapsulation controller tsib16130 may determinewhether to decapsulate an input packet stream. When decapsulation isperformed, the packet stream may be delivered to a link layer headerparser tsib16140. When decapsulation is not performed, the packet streammay be delivered to an output buffer tsib16220. The signalinginformation received from the scheduler tsib16020 may be used todetermine whether to perform decapsulation.

The link layer header parser tsib16140 may identify a header of thedelivered link layer packet. It is possible to identify a configurationof an IP packet included in a payload of the link layer packet byidentifying the header. For example, the IP packet may be segmented orconcatenated.

A packet configuration table tsib16150 may include payload informationof segmented and/or concatenated link layer packets. The transmitter andthe receiver may have the same information in the packet configurationtable tsib16150. The transmitter and the receiver may refer to theinformation of the packet configuration table tsib16150. It is possibleto find a value necessary for reassembly based on index informationincluded in the link layer packet.

A reassembly block tsib16160 may configure payloads of the segmentedand/or concatenated link layer packets as packets of an original IPstream. Segments may be collected and reconfigured as one IP packet, orconcatenated packets may be separated and reconfigured as a plurality ofIP packet streams. Recombined IP packets may be delivered to theoverhead processing part.

The overhead processing part may perform an operation of restoring apacket subjected to overhead reduction to an original packet as areverse operation of overhead reduction performed in the transmitter.This operation may be referred to as overhead processing. It is possibleto configure overhead processing parts corresponding to the number ofDPs that can be simultaneously decoded in the physical layer.

A packet recovery buffer tsib16170 may function as a buffer thatreceives a decapsulated RoHC packet or IP packet to perform overheadprocessing.

An overhead controller tsib16180 may determine whether to recover and/ordecompress the decapsulated packet. When recovery and/or decompressionare performed, the packet may be delivered to a packet stream recoveryblock tsib16190. When recovery and/or decompression are not performed,the packet may be delivered to the output buffer tsib16220. Whether toperform recovery and/or decompression may be determined based on thesignaling information delivered by the scheduler tsib16020.

The packet stream recovery block tsib16190 may perform an operation ofintegrating a packet stream separated from the transmitter with contextinformation of the packet stream. This operation may be a process ofrestoring a packet stream such that an RoHC decompressor tsib16210 canperform processing. In this process, it is possible to receive signalinginformation and/or context information from a signaling and/or contextcontroller tsib16200. The signaling and/or context controller tsib16200may determine signaling information delivered from the transmitter, anddeliver the signaling information to the packet stream recovery blocktsib16190 such that the signaling information may be mapped to a streamcorresponding to a context ID.

The RoHC decompressor tsib16210 may restore headers of packets of thepacket stream. The packets of the packet stream may be restored to formsof original IP packets through restoration of the headers. In otherwords, the RoHC decompressor tsib16210 may perform overhead processing.

The output buffer tsib16220 may function as a buffer before an outputstream is delivered to an IP layer tsib16230.

The link layers of the transmitter and the receiver proposed in thepresent invention may include the blocks or modules described above. Inthis way, the link layer may independently operate irrespective of anupper layer and a lower layer, overhead reduction may be efficientlyperformed, and a supportable function according to an upper/lower layermay be easily defined/added/deleted.

FIG. 17 illustrates a configuration of signaling transmission through alink layer according to an embodiment of the present invention(transmitting/receiving sides).

In the present invention, a plurality of service providers(broadcasters) may provide services within one frequency band. Inaddition, a service provider may provide a plurality of services, andone service may include one or more components. It can be consideredthat the user receives content using a service as a unit.

The present invention presumes that a transmission protocol based on aplurality of sessions is used to support an IP hybrid broadcast.Signaling information delivered through a signaling path may bedetermined based on a transmission configuration of each protocol.Various names may be applied to respective protocols according to agiven embodiment.

In the illustrated data configuration tsib17010 on the transmittingside, service providers (broadcasters) may provide a plurality ofservices (Service #1, #2, . . . ). In general, a signal for a servicemay be transmitted through a general transmission session (signaling C).However, the signal may be transmitted through a particular session(dedicated session) according to a given embodiment (signaling B).

Service data and service signaling information may be encapsulatedaccording to a transmission protocol. According to a given embodiment,an IP/UDP layer may be used. According to a given embodiment, a signalin the IP/UDP layer (signaling A) may be additionally provided. Thissignaling may be omitted.

Data processed using the IP/UDP may be input to the link layer. Asdescribed in the foregoing, overhead reduction and/or encapsulation maybe performed in the link layer. Here, link layer signaling may beadditionally provided. Link layer signaling may include a systemparameter, etc. Link layer signaling has been described above.

The service data and the signaling information subjected to the aboveprocess may be processed through PLPs in a physical layer. Here, a PLPmay be referred to as a DP. The example illustrated in the figurepresumes a case in which a base DP/PLP is used. However, depending onembodiments, transmission may be performed using only a general DP/PLPwithout the base DP/PLP.

In the example illustrated in the figure, a particular channel(dedicated channel) such as an FIC, an EAC, etc. is used. A signaldelivered through the FIC may be referred to as a fast information table(FIT), and a signal delivered through the EAC may be referred to as anemergency alert table (EAT). The FIT may be identical to theabove-described SLT. The particular channels may not be used dependingon embodiments. When the particular channel (dedicated channel) is notconfigured, the FIT and the EAT may be transmitted using a general linklayer signaling transmission scheme, or transmitted using a PLP via theIP/UDP as other service data.

According to a given embodiment, system parameters may include atransmitter-related parameter, a service provider-related parameter,etc. Link layer signaling may include IP header compression-relatedcontext information and/or identification information of data to whichthe context is applied. Signaling of an upper layer may include an IPaddress, a UDP number, service/component information, emergencyalert-related information, an IP/UDP address for service signaling, asession ID, etc. Detailed examples thereof have been described above.

In the illustrated data configuration tsib17020 on the receiving side,the receiver may decode only a PLP for a corresponding service usingsignaling information without having to decode all PLPs.

First, when the user selects or changes a service desired to bereceived, the receiver may be tuned to a corresponding frequency and mayread receiver information related to a corresponding channel stored in aDB, etc. The information stored in the DB, etc. of the receiver may beconfigured by reading an SLT at the time of initial channel scan.

After receiving the SLT and the information about the correspondingchannel, information previously stored in the DB is updated, andinformation about a transmission path of the service selected by theuser and information about a path, through which component informationis acquired or a signal necessary to acquire the information istransmitted, are acquired. When the information is not determined to bechanged using version information of the SLT, decoding or parsing may beomitted.

The receiver may verify whether SLT information is included in a PLP byparsing physical signaling of the PLP in a corresponding broadcaststream (not illustrated), which may be indicated through a particularfield of physical signaling. It is possible to access a position atwhich a service layer signal of a particular service is transmitted byaccessing the SLT information. The service layer signal may beencapsulated into the IP/UDP and delivered through a transmissionsession. It is possible to acquire information about a componentincluded in the service using this service layer signaling. A specificSLT-SLS configuration is as described above.

In other words, it is possible to acquire transmission path information,for receiving upper layer signaling information (service signalinginformation) necessary to receive the service, corresponding to one ofseveral packet streams and PLPs currently transmitted on a channel usingthe SLT. The transmission path information may include an IP address, aUDP port number, a session ID, a PLP ID, etc. Here, depending onembodiments, a value previously designated by the IANA or a system maybe used as an IP/UDP address. The information may be acquired using ascheme of accessing a DB or a shared memory, etc.

When the link layer signal and service data are transmitted through thesame PLP, or only one PLP is operated, service data delivered throughthe PLP may be temporarily stored in a device such as a buffer, etc.while the link layer signal is decoded.

It is possible to acquire information about a path through which theservice is actually transmitted using service signaling information of aservice to be received. In addition, a received packet stream may besubjected to decapsulation and header recovery using information such asoverhead reduction for a PLP to be received, etc.

In the illustrated example (tsib17020), the FIC and the EAC are used,and a concept of the base DP/PLP is presumed. As described in theforegoing, concepts of the FIC, the EAC, and the base DP/PLP may not beused.

While MISO or MIMO uses two antennas in the following for convenience ofdescription, the present invention is applicable to systems using two ormore antennas. The present invention proposes a physical profile (orsystem) optimized to minimize receiver complexity while attaining theperformance required for a particular use case. Physical (PHY) profiles(base, handheld and advanced profiles) according to an embodiment of thepresent invention are subsets of all configurations that a correspondingreceiver should implement. The PHY profiles share most of the functionalblocks but differ slightly in specific blocks and/or parameters. For thesystem evolution, future profiles may also be multiplexed with existingprofiles in a single radio frequency (RF) channel through a futureextension frame (FEF). The base profile and the handheld profileaccording to the embodiment of the present invention refer to profilesto which MIMO is not applied, and the advanced profile refers to aprofile to which MIMO is applied. The base profile may be used as aprofile for both the terrestrial broadcast service and the mobilebroadcast service. That is, the base profile may be used to define aconcept of a profile which includes the mobile profile. In addition, theadvanced profile may be divided into an advanced profile for a baseprofile with MIMO and an advanced profile for a handheld profile withMIMO. Moreover, the profiles may be changed according to intention ofthe designer.

The following terms and definitions may be applied to the presentinvention. The following terms and definitions may be changed accordingto design.

Auxiliary stream: sequence of cells carrying data of as yet undefinedmodulation and coding, which may be used for future extensions or asrequired by broadcasters or network operators

Base data pipe: data pipe that carries service signaling data

Baseband frame (or BBFRAME): set of Kbch bits which form the input toone FEC encoding process (BCH and LDPC encoding)

Cell: modulation value that is carried by one carrier of orthogonalfrequency division multiplexing (OFDM) transmission

Coded block: LDPC-encoded block of PLS1 data or one of the LDPC-encodedblocks of PLS2 data

Data pipe: logical channel in the physical layer that carries servicedata or related metadata, which may carry one or a plurality ofservice(s) or service component(s).

Data pipe unit (DPU): a basic unit for allocating data cells to a DP ina frame.

Data symbol: OFDM symbol in a frame which is not a preamble symbol (thedata symbol encompasses the frame signaling symbol and frame edgesymbol)

DP_ID: this 8-bit field identifies uniquely a DP within the systemidentified by the SYSTEM_ID

Dummy cell: cell carrying a pseudo-random value used to fill theremaining capacity not used for PLS signaling, DPs or auxiliary streams

Emergency alert channel (EAC): part of a frame that carries EASinformation data

Frame: physical layer time slot that starts with a preamble and endswith a frame edge symbol

Frame repetition unit: a set of frames belonging to the same ordifferent physical layer profiles including an FEF, which is repeatedeight times in a superframe

Fast information channel (FIC): a logical channel in a frame thatcarries mapping information between a service and the corresponding baseDP

FECBLOCK: set of LDPC-encoded bits of DP data

FFT size: nominal FFT size used for a particular mode, equal to theactive symbol period Ts expressed in cycles of an elementary period T

Frame signaling symbol: OFDM symbol with higher pilot density used atthe start of a frame in certain combinations of FFT size, guard intervaland scattered pilot pattern, which carries a part of the PLS data

Frame edge symbol: OFDM symbol with higher pilot density used at the endof a frame in certain combinations of FFT size, guard interval andscattered pilot pattern

Frame group: the set of all frames having the same PHY profile type in asuperframe

Future extension frame: physical layer time slot within the superframethat may be used for future extension, which starts with a preamble

Futurecast UTB system: proposed physical layer broadcast system, theinput of which is one or more MPEG2-TS, IP or general stream(s) and theoutput of which is an RF signal

Input stream: a stream of data for an ensemble of services delivered tothe end users by the system

Normal data symbol: data symbol excluding the frame signaling symbol andthe frame edge symbol

PHY profile: subset of all configurations that a corresponding receivershould implement

PLS: physical layer signaling data including PLS1 and PLS2

PLS1: a first set of PLS data carried in a frame signaling symbol (FSS)having a fixed size, coding and modulation, which carries basicinformation about a system as well as parameters needed to decode PLS2

NOTE: PLS1 data remains constant for the duration of a frame group

PLS2: a second set of PLS data transmitted in the FSS, which carriesmore detailed PLS data about the system and the DPs

PLS2 dynamic data: PLS2 data that dynamically changes frame-by-frame

PLS2 static data: PLS2 data that remains static for the duration of aframe group

Preamble signaling data: signaling data carried by the preamble symboland used to identify the basic mode of the system

Preamble symbol: fixed-length pilot symbol that carries basic PLS dataand is located at the beginning of a frame

The preamble symbol is mainly used for fast initial band scan to detectthe system signal, timing thereof, frequency offset, and FFT size.

Reserved for future use: not defined by the present document but may bedefined in future

Superframe: set of eight frame repetition units

Time interleaving block (TI block): set of cells within which timeinterleaving is carried out, corresponding to one use of a timeinterleaver memory

TI group: unit over which dynamic capacity allocation for a particularDP is carried out, made up of an integer, dynamically varying number ofXFECBLOCKs

NOTE: The TI group may be mapped directly to one frame or may be mappedto a plurality of frames. The TI group may contain one or more TIblocks.

Type 1 DP: DP of a frame where all DPs are mapped to the frame in timedivision multiplexing (TDM) scheme

Type 2 DP: DP of a frame where all DPs are mapped to the frame infrequency division multiplexing (FDM) scheme

XFECBLOCK: set of N_(cells) cells carrying all the bits of one LDPCFECBLOCK

FIG. 18 illustrates a configuration of a broadcast signal transmissionapparatus for future broadcast services according to an embodiment ofthe present invention.

The broadcast signal transmission apparatus for future broadcastservices according to the present embodiment may include an inputformatting block 1000, a bit interleaved coding & modulation (BICM)block 1010, a frame building block 1020, an OFDM generation block 1030and a signaling generation block 1040. Description will be given of anoperation of each block of the broadcast signal transmission apparatus.

In input data according to an embodiment of the present invention, IPstream/packets and MPEG2-TS may be main input formats, and other streamtypes are handled as general streams. In addition to these data inputs,management information is input to control scheduling and allocation ofthe corresponding bandwidth for each input stream. In addition, thepresent invention allows simultaneous input of one or a plurality of TSstreams, IP stream(s) and/or a general stream(s).

The input formatting block 1000 may demultiplex each input stream intoone or a plurality of data pipes, to each of which independent codingand modulation are applied. A DP is the basic unit for robustnesscontrol, which affects QoS. One or a plurality of services or servicecomponents may be carried by one DP. The DP is a logical channel in aphysical layer for delivering service data or related metadata capableof carrying one or a plurality of services or service components.

In addition, a DPU is a basic unit for allocating data cells to a DP inone frame.

An input to the physical layer may include one or a plurality of datastreams. Each of the data streams is delivered by one DP. The inputformatting block 1000 may covert a data stream input through one or morephysical paths (or DPs) into a baseband frame (BBF). In this case, theinput formatting block 1000 may perform null packet deletion or headercompression on input data (a TS or IP input stream) in order to enhancetransmission efficiency. A receiver may have a priori information for aparticular part of a header, and thus this known information may bedeleted from a transmitter. A null packet deletion block 3030 may beused only for a TS input stream.

In the BICM block 1010, parity data is added for error correction andencoded bit streams are mapped to complex-value constellation symbols.The symbols are interleaved across a specific interleaving depth that isused for the corresponding DP. For the advanced profile, MIMO encodingis performed in the BICM block 1010 and an additional data path is addedat the output for MIMO transmission.

The frame building block 1020 may map the data cells of the input DPsinto the OFDM symbols within a frame, and perform frequency interleavingfor frequency-domain diversity, especially to combat frequency-selectivefading channels. The frame building block 1020 may include a delaycompensation block, a cell mapper and a frequency interleaver.

The delay compensation block may adjust timing between DPs andcorresponding PLS data to ensure that the DPs and the corresponding PLSdata are co-timed at a transmitter side. The PLS data is delayed by thesame amount as the data pipes by addressing the delays of data pipescaused by the input formatting block and BICM block. The delay of theBICM block is mainly due to the time interleaver. In-band signaling datacarries information of the next TI group so that the information iscarried one frame ahead of the DPs to be signaled. The delaycompensation block delays in-band signaling data accordingly.

The cell mapper may map PLS, DPs, auxiliary streams, dummy cells, etc.to active carriers of the OFDM symbols in the frame. The basic functionof the cell mapper 7010 is to map data cells produced by the TIs foreach of the DPs, PLS cells, and EAC/FIC cells, if any, into arrays ofactive OFDM cells corresponding to each of the OFDM symbols within aframe. A basic function of the cell mapper is to map a data cellgenerated by time interleaving for each DP and PLS cell to an array ofactive OFDM cells (if present) corresponding to respective OFDM symbolsin one frame. Service signaling data (such as program specificinformation (PSI)/SI) may be separately gathered and sent by a DP. Thecell mapper operates according to dynamic information produced by ascheduler and the configuration of a frame structure. The frequencyinterleaver may randomly interleave data cells received from the cellmapper to provide frequency diversity. In addition, the frequencyinterleaver may operate on an OFDM symbol pair including two sequentialOFDM symbols using a different interleaving-seed order to obtain maximuminterleaving gain in a single frame.

The OFDM generation block 1030 modulates OFDM carriers by cells producedby the frame building block, inserts pilots, and produces a time domainsignal for transmission. In addition, this block subsequently insertsguard intervals, and applies peak-to-average power ratio (PAPR)reduction processing to produce a final RF signal.

Specifically, after inserting a preamble at the beginning of each frame,the OFDM generation block 1030 may apply conventional OFDM modulationhaving a cyclic prefix as a guard interval. For antenna space diversity,a distributed MISO scheme is applied across transmitters. In addition, aPAPR scheme is performed in the time domain. For flexible networkplanning, the present invention provides a set of various FFT sizes,guard interval lengths and corresponding pilot patterns.

In addition, the present invention may multiplex signals of a pluralityof broadcast transmission/reception systems in the time domain such thatdata of two or more different broadcast transmission/reception systemsproviding broadcast services may be simultaneously transmitted in thesame RF signal bandwidth. In this case, the two or more differentbroadcast transmission/reception systems refer to systems providingdifferent broadcast services. The different broadcast services may referto a terrestrial broadcast service, mobile broadcast service, etc.

The signaling generation block 1040 may create physical layer signalinginformation used for an operation of each functional block. Thissignaling information is also transmitted so that services of interestare properly recovered at a receiver side. Signaling informationaccording to an embodiment of the present invention may include PLSdata. PLS provides the receiver with a means to access physical layerDPs. The PLS data includes PLS1 data and PLS2 data.

The PLS1 data is a first set of PLS data carried in an FSS symbol in aframe having a fixed size, coding and modulation, which carries basicinformation about the system in addition to the parameters needed todecode the PLS2 data. The PLS1 data provides basic transmissionparameters including parameters required to enable reception anddecoding of the PLS2 data. In addition, the PLS1 data remains constantfor the duration of a frame group.

The PLS2 data is a second set of PLS data transmitted in an FSS symbol,which carries more detailed PLS data about the system and the DPs. ThePLS2 contains parameters that provide sufficient information for thereceiver to decode a desired DP. The PLS2 signaling further includes twotypes of parameters, PLS2 static data (PLS2-STAT data) and PLS2 dynamicdata (PLS2-DYN data). The PLS2 static data is PLS2 data that remainsstatic for the duration of a frame group and the PLS2 dynamic data isPLS2 data that dynamically changes frame by frame. Details of the PLSdata will be described later.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 19 illustrates a BICM block according to an embodiment of thepresent invention.

The BICM block illustrated in FIG. 19 corresponds to an embodiment ofthe BICM block 1010 described with reference to FIG. 18.

As described above, the broadcast signal transmission apparatus forfuture broadcast services according to the embodiment of the presentinvention may provide a terrestrial broadcast service, mobile broadcastservice, UHDTV service, etc.

Since QoS depends on characteristics of a service provided by thebroadcast signal transmission apparatus for future broadcast servicesaccording to the embodiment of the present invention, data correspondingto respective services needs to be processed using different schemes.Accordingly, the BICM block according to the embodiment of the presentinvention may independently process respective DPs by independentlyapplying SISO, MISO and MIMO schemes to data pipes respectivelycorresponding to data paths. Consequently, the broadcast signaltransmission apparatus for future broadcast services according to theembodiment of the present invention may control QoS for each service orservice component transmitted through each DP.

(a) shows a BICM block applied to a profile (or system) to which MIMO isnot applied, and (b) shows a BICM block of a profile (or system) towhich MIMO is applied.

The BICM block to which MIMO is not applied and the BICM block to whichMIMO is applied may include a plurality of processing blocks forprocessing each DP.

Description will be given of each processing block of the BICM block towhich MIMO is not applied and the BICM block to which MIMO is applied.

A processing block 5000 of the BICM block to which MIMO is not appliedmay include a data FEC encoder 5010, a bit interleaver 5020, aconstellation mapper 5030, a signal space diversity (SSD) encoding block5040 and a time interleaver 5050.

The data FEC encoder 5010 performs FEC encoding on an input BBF togenerate FECBLOCK procedure using outer coding (BCH) and inner coding(LDPC). The outer coding (BCH) is optional coding method. A detailedoperation of the data FEC encoder 5010 will be described later.

The bit interleaver 5020 may interleave outputs of the data FEC encoder5010 to achieve optimized performance with a combination of LDPC codesand a modulation scheme while providing an efficiently implementablestructure. A detailed operation of the bit interleaver 5020 will bedescribed later.

The constellation mapper 5030 may modulate each cell word from the bitinterleaver 5020 in the base and the handheld profiles, or each cellword from the cell-word demultiplexer 5010-1 in the advanced profileusing either QPSK, QAM-16, non-uniform QAM (NUQ-64, NUQ-256, orNUQ-1024) or non-uniform constellation (NUC-16, NUC-64, NUC-256, orNUC-1024) mapping to give a power-normalized constellation point, e₁.This constellation mapping is applied only for DPs. It is observed thatQAM-16 and NUQs are square shaped, while NUCs have arbitrary shapes.When each constellation is rotated by any multiple of 90 degrees, therotated constellation exactly overlaps with its original one. This“rotation-sense” symmetric property makes the capacities and the averagepowers of the real and imaginary components equal to each other. BothNUQs and NUCs are defined specifically for each code rate and theparticular one used is signaled by the parameter DP_MOD filed in thePLS2 data.

The time interleaver 5050 may operates at a DP level. Parameters of timeinterleaving (TI) may be set differently for each DP. A detailedoperation of the time interleaver 5050 will be described later.

A processing block 5000-1 of the BICM block to which MIMO is applied mayinclude the data FEC encoder, the bit interleaver, the constellationmapper, and the time interleaver.

However, the processing block 5000-1 is distinguished from theprocessing block 5000 of the BICM block to which MIMO is not applied inthat the processing block 5000-1 further includes a cell-worddemultiplexer 5010-1 and a MIMO encoding block 5020-1.

In addition, operations of the data FEC encoder, the bit interleaver,the constellation mapper, and the time interleaver in the processingblock 5000-1 correspond to those of the data FEC encoder 5010, the bitinterleaver 5020, the constellation mapper 5030, and the timeinterleaver 5050 described above, and thus description thereof isomitted.

The cell-word demultiplexer 5010-1 is used for a DP of the advancedprofile to divide a single cell-word stream into dual cell-word streamsfor MIMO processing.

The MIMO encoding block 5020-1 may process an output of the cell-worddemultiplexer 5010-1 using a MIMO encoding scheme. The MIMO encodingscheme is optimized for broadcast signal transmission. MIMO technologyis a promising way to obtain a capacity increase but depends on channelcharacteristics. Especially for broadcasting, a strong LOS component ofa channel or a difference in received signal power between two antennascaused by different signal propagation characteristics makes itdifficult to obtain capacity gain from MIMO. The proposed MIMO encodingscheme overcomes this problem using rotation-based precoding and phaserandomization of one of MIMO output signals.

MIMO encoding is intended for a 2x2 MIMO system requiring at least twoantennas at both the transmitter and the receiver. A MIMO encoding modeof the present invention may be defined as full-rate spatialmultiplexing (FR-SM). FR-SM encoding may provide capacity increase withrelatively small complexity increase at the receiver side. In addition,the MIMO encoding scheme of the present invention has no restriction onan antenna polarity configuration.

MIMO processing is applied at the DP level. NUQ (e_(1,i) and e_(2,i))corresponding to a pair of constellation mapper outputs is fed to aninput of a MIMO encoder. Paired MIMO encoder output (g1,i and g2,i) istransmitted by the same carrier k and OFDM symbol 1 of respective TXantennas thereof.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 20 illustrates a BICM block according to another embodiment of thepresent invention.

The BICM block illustrated in FIG. 20 corresponds to another embodimentof the BICM block 1010 described with reference to FIG. 18.

FIG. 20 illustrates a BICM block for protection of physical layersignaling (PLS), an emergency alert channel (EAC) and a fast informationchannel (FIC). The EAC is a part of a frame that carries EAS informationdata, and the FIC is a logical channel in a frame that carries mappinginformation between a service and a corresponding base DP. Details ofthe EAC and FIC will be described later.

Referring to FIG. 20, the BICM block for protection of the PLS, the EACand the FIC may include a PLS FEC encoder 6000, a bit interleaver 6010and a constellation mapper 6020.

In addition, the PLS FEC encoder 6000 may include a scrambler, a BCHencoding/zero insertion block, an LDPC encoding block and an LDPC paritypuncturing block. Description will be given of each block of the BICMblock.

The PLS FEC encoder 6000 may encode scrambled PLS ½ data, EAC and FICsections.

The scrambler may scramble PLS1 data and PLS2 data before BCH encodingand shortened and punctured LDPC encoding.

The BCH encoding/zero insertion block may perform outer encoding on thescrambled PLS ½ data using a shortened BCH code for PLS protection, andinsert zero bits after BCH encoding. For PLS1 data only, output bits ofzero insertion may be permutted before LDPC encoding.

The LDPC encoding block may encode an output of the BCH encoding/zeroinsertion block using an LDPC code. To generate a complete coded block,C_(ldpc) and parity bits P_(ldpc) are encoded systematically from eachzero-inserted PLS information block I_(ldpc) and appended thereto.C _(ldpc)=[I _(ldpc) P _(ldpc)]=[i ₀ ,i ₁ , . . . ,i _(K) _(ldpc) ₋₁ ,p₀ ,p ₁ , . . . ,p _(N) _(ldpc) _(-K) _(ldpc) ₋₁]   [Equation 1]

The LDPC parity puncturing block may perform puncturing on the PLS1 dataand the PLS2 data.

When shortening is applied to PLS1 data protection, some LDPC paritybits are punctured after LDPC encoding. In addition, for PLS2 dataprotection, LDPC parity bits of PLS2 are punctured after LDPC encoding.These punctured bits are not transmitted.

The bit interleaver 6010 may interleave each of shortened and puncturedPLS1 data and PLS2 data.

The constellation mapper 6020 may map the bit-interleaved PLS1 data andPLS2 data to constellations.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 21 illustrates a bit interleaving process of PLS according to anembodiment of the present invention.

Each shortened and punctured PLS1 and PLS2 coded block is interleavedbit-by-bit as described in FIG. 22. Each block of additional parity bitsis interleaved with the same block interleaving structure butseparately.

In the case of BPSK, there are two branches for bit interleaving toduplicate FEC coded bits in the real and imaginary parts. Each codedblock is written to the upper branch first. The bits are mapped to thelower branch by applying modulo N_(FEC) addition with cyclic shiftingvalue floor(N_(FEC)/2), where N_(FEC) is the length of each LDPC codedblock after shortening and puncturing.

In other modulation cases, such as QSPK, QAM-16 and NUQ-64, FEC codedbits are written serially into the interleaver column-wise, where thenumber of columns is the same as the modulation order.

In the read operation, the bits for one constellation symbol are readout sequentially row-wise and fed into the bit demultiplexer block.These operations are continued until the end of the column

Each bit interleaved group is demultiplexed bit-by-bit in a group beforeconstellation mapping. Depending on modulation order, there are twomapping rules. In the case of BPSK and QPSK, the reliability of bits ina symbol is equal. Therefore, the bit group read out from the bitinterleaving block is mapped to a QAM symbol without any operation.

In the cases of QAM-16 and NUQ-64 mapped to a QAM symbol, the rule ofoperation is described in FIG. 23(a). As shown in FIG. 23(a), i is bitgroup index corresponding to column index in bit interleaving.

FIG. 21 shows the bit demultiplexing rule for QAM-16. This operationcontinues until all bit groups are read from the bit interleaving block.

FIG. 22 illustrates a configuration of a broadcast signal receptionapparatus for future broadcast services according to an embodiment ofthe present invention.

The broadcast signal reception apparatus for future broadcast servicesaccording to the embodiment of the present invention may correspond tothe broadcast signal transmission apparatus for future broadcastservices described with reference to FIG. 18.

The broadcast signal reception apparatus for future broadcast servicesaccording to the embodiment of the present invention may include asynchronization & demodulation module 9000, a frame parsing module 9010,a demapping & decoding module 9020, an output processor 9030 and asignaling decoding module 9040. A description will be given of operationof each module of the broadcast signal reception apparatus.

The synchronization & demodulation module 9000 may receive input signalsthrough m Rx antennas, perform signal detection and synchronization withrespect to a system corresponding to the broadcast signal receptionapparatus, and carry out demodulation corresponding to a reverseprocedure of a procedure performed by the broadcast signal transmissionapparatus.

The frame parsing module 9010 may parse input signal frames and extractdata through which a service selected by a user is transmitted. If thebroadcast signal transmission apparatus performs interleaving, the frameparsing module 9010 may carry out deinterleaving corresponding to areverse procedure of interleaving. In this case, positions of a signaland data that need to be extracted may be obtained by decoding dataoutput from the signaling decoding module 9040 to restore schedulinginformation generated by the broadcast signal transmission apparatus.

The demapping & decoding module 9020 may convert input signals into bitdomain data and then deinterleave the same as necessary. The demapping &decoding module 9020 may perform demapping of mapping applied fortransmission efficiency and correct an error generated on a transmissionchannel through decoding. In this case, the demapping & decoding module9020 may obtain transmission parameters necessary for demapping anddecoding by decoding data output from the signaling decoding module9040.

The output processor 9030 may perform reverse procedures of variouscompression/signal processing procedures which are applied by thebroadcast signal transmission apparatus to improve transmissionefficiency. In this case, the output processor 9030 may acquirenecessary control information from data output from the signalingdecoding module 9040. An output of the output processor 9030 correspondsto a signal input to the broadcast signal transmission apparatus and maybe MPEG-TSs, IP streams (v4 or v6) and generic streams.

The signaling decoding module 9040 may obtain PLS information from asignal demodulated by the synchronization & demodulation module 9000. Asdescribed above, the frame parsing module 9010, the demapping & decodingmodule 9020 and the output processor 9030 may execute functions thereofusing data output from the signaling decoding module 9040.

A frame according to an embodiment of the present invention is furtherdivided into a number of OFDM symbols and a preamble. As shown in (d),the frame includes a preamble, one or more frame signaling symbols(FSSs), normal data symbols and a frame edge symbol (FES).

The preamble is a special symbol that enables fast futurecast UTB systemsignal detection and provides a set of basic transmission parameters forefficient transmission and reception of a signal. Details of thepreamble will be described later.

A main purpose of the FSS is to carry PLS data. For fast synchronizationand channel estimation, and hence fast decoding of PLS data, the FSS hasa dense pilot pattern than a normal data symbol. The FES has exactly thesame pilots as the FSS, which enables frequency-only interpolationwithin the FES and temporal interpolation, without extrapolation, forsymbols immediately preceding the FES.

FIG. 23 illustrates a signaling hierarchy structure of a frame accordingto an embodiment of the present invention.

FIG. 23 illustrates the signaling hierarchy structure, which is splitinto three main parts corresponding to preamble signaling data 11000,PLS1 data 11010 and PLS2 data 11020. A purpose of a preamble, which iscarried by a preamble symbol in every frame, is to indicate atransmission type and basic transmission parameters of the frame. PLS1enables the receiver to access and decode the PLS2 data, which containsthe parameters to access a DP of interest. PLS2 is carried in everyframe and split into two main parts corresponding to PLS2-STAT data andPLS2-DYN data. Static and dynamic portions of PLS2 data are followed bypadding, if necessary.

Preamble signaling data according to an embodiment of the presentinvention carries 21 bits of information that are needed to enable thereceiver to access PLS data and trace DPs within the frame structure.Details of the preamble signaling data are as follows.

FFT_SIZE: This 2-bit field indicates an FFT size of a current framewithin a frame group as described in the following Table 1.

TABLE 1 Value FFT size 00  8K FFT 01 16K FFT 10 32K FFT 11 Reserved

GI_FRACTION: This 3-bit field indicates a guard interval fraction valuein a current superframe as described in the following Table 2.

TABLE 2 Value GI_FRACTION 000 1/5  001 1/10 010 1/20 011 1/40 100 1/80101  1/160 110 to 111 Reserved

EAC_FLAG: This 1-bit field indicates whether the EAC is provided in acurrent frame. If this field is set to ‘1’, an emergency alert service(EAS) is provided in the current frame. If this field set to ‘0’, theEAS is not carried in the current frame. This field may be switcheddynamically within a superframe.

PILOT_MODE: This 1-bit field indicates whether a pilot mode is a mobilemode or a fixed mode for a current frame in a current frame group. Ifthis field is set to ‘0’, the mobile pilot mode is used. If the field isset to ‘1’, the fixed pilot mode is used.

PAPR_FLAG: This 1-bit field indicates whether PAPR reduction is used fora current frame in a current frame group. If this field is set to avalue of ‘1’, tone reservation is used for PAPR reduction. If this fieldis set to a value of ‘0’, PAPR reduction is not used.

RESERVED: This 7-bit field is reserved for future use.

FIG. 24 illustrates PLS1 data according to an embodiment of the presentinvention.

PLS1 data provides basic transmission parameters including parametersrequired to enable reception and decoding of PLS2. As mentioned above,the PLS1 data remain unchanged for the entire duration of one framegroup. A detailed definition of the signaling fields of the PLS1 data isas follows.

PREAMBLE_DATA: This 20-bit field is a copy of preamble signaling dataexcluding EAC_FLAG.

NUM_FRAME_FRU: This 2-bit field indicates the number of the frames perFRU.

PAYLOAD_TYPE: This 3-bit field indicates a format of payload datacarried in a frame group. PAYLOAD_TYPE is signaled as shown in Table 3.

TABLE 3 Value Payload type 1XX TS is transmitted. X1X IP stream istransmitted. XX1 GS is transmitted.

NUM_FSS: This 2-bit field indicates the number of FSSs in a currentframe.

SYSTEM_VERSION: This 8-bit field indicates a version of a transmittedsignal format. SYSTEM_VERSION is divided into two 4-bit fields: a majorversion and a minor version.

Major version: The MSB corresponding to four bits of the SYSTEM_VERSIONfield indicate major version information. A change in the major versionfield indicates a non-backward-compatible change. A default value is‘0000’. For a version described in this standard, a value is set to‘0000’.

Minor version: The LSB corresponding to four bits of SYSTEM_VERSIONfield indicate minor version information. A change in the minor versionfield is backwards compatible.

CELL_ID: This is a 16-bit field which uniquely identifies a geographiccell in an ATSC network. An ATSC cell coverage area may include one ormore frequencies depending on the number of frequencies used perfuturecast UTB system. If a value of CELL_ID is not known orunspecified, this field is set to ‘0’.

NETWORK_ID: This is a 16-bit field which uniquely identifies a currentATSC network.

SYSTEM_ID: This 16-bit field uniquely identifies the futurecast UTBsystem within the ATSC network. The futurecast UTB system is aterrestrial broadcast system whose input is one or more input streams(TS, IP, GS) and whose output is an RF signal. The futurecast UTB systemcarries one or more PHY profiles and FEF, if any. The same futurecastUTB system may carry different input streams and use different RFs indifferent geographical areas, allowing local service insertion. Theframe structure and scheduling are controlled in one place and areidentical for all transmissions within the futurecast UTB system. One ormore futurecast UTB systems may have the same SYSTEM_ID meaning thatthey all have the same physical layer structure and configuration.

The following loop includes FRU_PHY_PROFILE, FRU_FRAME_LENGTH,FRU_GI_FRACTION, and RESERVED which are used to indicate an FRUconfiguration and a length of each frame type. A loop size is fixed sothat four PHY profiles (including an FEF) are signaled within the FRU.If NUM_FRAME_FRU is less than 4, unused fields are filled with zeros.

FRU_PHY_PROFILE: This 3-bit field indicates a PHY profile type of an(i+1)^(th) (i is a loop index) frame of an associated FRU. This fielduses the same signaling format as shown in Table 8.

FRU_FRAME_LENGTH: This 2-bit field indicates a length of an (i+1)^(th)frame of an associated FRU. Using FRU_FRAME_LENGTH together withFRU_GI_FRACTION, an exact value of a frame duration may be obtained.

FRU_GI_FRACTION: This 3-bit field indicates a guard interval fractionvalue of an (i+1)^(th) frame of an associated FRU. FRU_GI_FRACTION issignaled according to Table 7.

RESERVED: This 4-bit field is reserved for future use.

The following fields provide parameters for decoding the PLS2 data.

PLS2_FEC_TYPE: This 2-bit field indicates an FEC type used by PLS2protection. The FEC type is signaled according to Table 4. Details ofLDPC codes will be described later.

TABLE 4 Content PLS2 FEC type 00 4K-1/4 and 7K-3/10 LDPC codes 01 to 11Reserved

PLS2_MOD: This 3-bit field indicates a modulation type used by PLS2. Themodulation type is signaled according to Table 5.

TABLE 5 Value PLS2_MODE 000 BPSK 001 QPSK 010 QAM-16 011 NUQ-64 100 to111 Reserved

PLS2_SIZE_CELL: This 15-bit field indicates C_(total_partial_block), asize (specified as the number of QAM cells) of the collection of fullcoded blocks for PLS2 that is carried in a current frame group. Thisvalue is constant during the entire duration of the current frame group.

PLS2_STAT_SIZE_BIT: This 14-bit field indicates a size, in bits, ofPLS2-STAT for a current frame group. This value is constant during theentire duration of the current frame group.

PLS2_DYN_SIZE_BIT: This 14-bit field indicates a size, in bits, ofPLS2-DYN for a current frame group. This value is constant during theentire duration of the current frame group.

PLS2_REP_FLAG: This 1-bit flag indicates whether a PLS2 repetition modeis used in a current frame group. When this field is set to a value of‘1’, the PLS2 repetition mode is activated. When this field is set to avalue of ‘0’, the PLS2 repetition mode is deactivated.

PLS2_REP_SIZE_CELL: This 15-bit field indicates C_(total_partial_block),a size (specified as the number of QAM cells) of the collection ofpartial coded blocks for PLS2 carried in every frame of a current framegroup, when PLS2 repetition is used. If repetition is not used, a valueof this field is equal to 0. This value is constant during the entireduration of the current frame group.

PLS2_NEXT_FEC_TYPE: This 2-bit field indicates an FEC type used for PLS2that is carried in every frame of a next frame group. The FEC type issignaled according to Table 10.

PLS2_NEXT_MOD: This 3-bit field indicates a modulation type used forPLS2 that is carried in every frame of a next frame group. Themodulation type is signaled according to Table 11.

PLS2_NEXT_REP_FLAG: This 1-bit flag indicates whether the PLS2repetition mode is used in a next frame group. When this field is set toa value of ‘1’, the PLS2 repetition mode is activated. When this fieldis set to a value of ‘0’, the PLS2 repetition mode is deactivated.

PLS2_NEXT_REP_SIZE_CELL: This 15-bit field indicatesC_(total_full_block), a size (specified as the number of QAM cells) ofthe collection of full coded blocks for PLS2 that is carried in everyframe of a next frame group, when PLS2 repetition is used. If repetitionis not used in the next frame group, a value of this field is equal to0. This value is constant during the entire duration of a current framegroup.

PLS2_NEXT_REP_STAT_SIZE_BIT: This 14-bit field indicates a size, inbits, of PLS2-STAT for a next frame group. This value is constant in acurrent frame group.

PLS2_NEXT_REP_DYN_SIZE_BIT: This 14-bit field indicates the size, inbits, of the PLS2-DYN for a next frame group. This value is constant ina current frame group.

PLS2_AP_MODE: This 2-bit field indicates whether additional parity isprovided for PLS2 in a current frame group. This value is constantduring the entire duration of the current frame group. Table 6 belowprovides values of this field. When this field is set to a value of‘00’, additional parity is not used for the PLS2 in the current framegroup.

TABLE 6 Value PLS2-AP mode 00 AP is not provided 01 AP1 mode 10 to 11Reserved

PLS2_AP_SIZE_CELL: This 15-bit field indicates a size (specified as thenumber of QAM cells) of additional parity bits of PLS2. This value isconstant during the entire duration of a current frame group.

PLS2_NEXT_AP_MODE: This 2-bit field indicates whether additional parityis provided for PLS2 signaling in every frame of a next frame group.This value is constant during the entire duration of a current framegroup. Table 12 defines values of this field.

PLS2_NEXT_AP_SIZE_CELL: This 15-bit field indicates a size (specified asthe number of QAM cells) of additional parity bits of PLS2 in everyframe of a next frame group. This value is constant during the entireduration of a current frame group.

RESERVED: This 32-bit field is reserved for future use.

CRC_32: A 32-bit error detection code, which is applied to all PLS1signaling.

FIG. 25 illustrates PLS2 data according to an embodiment of the presentinvention.

FIG. 25 illustrates PLS2-STAT data of the PLS2 data. The PLS2-STAT datais the same within a frame group, while PLS2-DYN data providesinformation that is specific for a current frame.

Details of fields of the PLS2-STAT data are described below.

FIC_FLAG: This 1-bit field indicates whether the FIC is used in acurrent frame group. If this field is set to ‘1’, the FIC is provided inthe current frame. If this field set to ‘0’, the FIC is not carried inthe current frame. This value is constant during the entire duration ofa current frame group.

AUX_FLAG: This 1-bit field indicates whether an auxiliary stream is usedin a current frame group. If this field is set to ‘1’, the auxiliarystream is provided in a current frame. If this field set to ‘0’, theauxiliary stream is not carried in the current frame. This value isconstant during the entire duration of current frame group.

NUM_DP: This 6-bit field indicates the number of DPs carried within acurrent frame. A value of this field ranges from 1 to 64, and the numberof DPs is NUM_DP+1.

DP_ID: This 6-bit field identifies uniquely a DP within a PHY profile.

DP_TYPE: This 3-bit field indicates a type of a DP. This is signaledaccording to the following Table 7.

TABLE 7 Value DP Type 000 DP Type 1 001 DP Type 2 010 to 111 Reserved

DP_GROUP_ID: This 8-bit field identifies a DP group with which a currentDP is associated. This may be used by the receiver to access DPs ofservice components associated with a particular service having the sameDP_GROUP_ID.

BASE_DP_ID: This 6-bit field indicates a DP carrying service signalingdata (such as PSI/SI) used in a management layer. The DP indicated byBASE_DP_ID may be either a normal DP carrying the service signaling dataalong with service data or a dedicated DP carrying only the servicesignaling data.

DP_FEC_TYPE: This 2-bit field indicates an FEC type used by anassociated DP. The FEC type is signaled according to the following Table8.

TABLE 8 Value FEC_TYPE 00 16K LDPC 01 64K LDPC 10 to 11 Reserved

DP_COD: This 4-bit field indicates a code rate used by an associated DP.The code rate is signaled according to the following Table 9.

TABLE 9 Value Code rate 0000 5/15 0001 6/15 0010 7/15 0011 8/15 01009/15 0101 10/15  0110 11/15  0111 12/15  1000 13/15  1001 to 1111Reserved

DP_MOD: This 4-bit field indicates modulation used by an associated DP.The modulation is signaled according to the following Table 10.

TABLE 10 Value Modulation 0000 QPSK 0001 QAM-16 0010 NUQ-64 0011 NUQ-2560100 NUQ-1024 0101 NUC-16 0110 NUC-64 0111 NUC-256 1000 NUC-1024 1001 to1111 Reserved

DP_SSD_FLAG: This 1-bit field indicates whether an SSD mode is used inan associated DP. If this field is set to a value of ‘1’, SSD is used.If this field is set to a value of ‘0’, SSD is not used.

The following field appears only if PHY_PROFILE is equal to ‘010’, whichindicates the advanced profile:

DP_MIMO: This 3-bit field indicates which type of MIMO encoding processis applied to an associated DP. A type of MIMO encoding process issignaled according to the following Table 11.

TABLE 11 Value MIMO encoding 000 FR-SM 001 FRFD-SM 010 to 111 Reserved

DP_TI_TYPE: This 1-bit field indicates a type of time interleaving. Avalue of ‘0’ indicates that one TI group corresponds to one frame andcontains one or more TI blocks. A value of ‘1’ indicates that one TIgroup is carried in more than one frame and contains only one TI block.

DP_TI_LENGTH: The use of this 2-bit field (allowed values are only 1, 2,4, and 8) is determined by values set within the DP_TI_TYPE field asfollows.

If DP_TI_TYPE is set to a value of ‘1’, this field indicates P_(I), thenumber of frames to which each TI group is mapped, and one TI block ispresent per TI group (N_(TI)=1). Allowed values of P_(I) with the 2-bitfield are defined in Table 12 below.

If DP_TI_TYPE is set to a value of ‘0’, this field indicates the numberof TI blocks N_(TI) per TI group, and one TI group is present per frame(P_(I)=1). Allowed values of P_(I) with the 2-bit field are defined inthe following Table 12.

TABLE 12 2-bit field P_(I) N_(TI) 00 1 1 01 2 2 10 4 3 11 8 4

DP_FRAME_INTERVAL: This 2-bit field indicates a frame interval(I_(JUMP)) within a frame group for an associated DP and allowed valuesare 1, 2, 4, and 8 (the corresponding 2-bit field is ‘00’, ‘01’, ‘10’,or ‘11’, respectively). For DPs that do not appear every frame of theframe group, a value of this field is equal to an interval betweensuccessive frames. For example, if a DP appears on frames 1, 5, 9, 13,etc., this field is set to a value of ‘4’. For DPs that appear in everyframe, this field is set to a value of ‘1’.

DP_TI_BYPASS: This 1-bit field determines availability of the timeinterleaver 5050. If time interleaving is not used for a DP, a value ofthis field is set to ‘1’. If time interleaving is used, the value is setto ‘0’.

DP_FIRST_FRAME_IDX: This 5-bit field indicates an index of a first frameof a superframe in which a current DP occurs. A value ofDP_FIRST_FRAME_IDX ranges from 0 to 31.

DP_NUM_BLOCK_MAX: This 10-bit field indicates a maximum value ofDP_NUM_BLOCKS for this DP. A value of this field has the same range asDP_NUM_BLOCKS.

DP_PAYLOAD_TYPE: This 2-bit field indicates a type of payload datacarried by a given DP. DP_PAYLOAD_TYPE is signaled according to thefollowing Table 13.

TABLE 13 Value Payload type 00 TS 01 IP 10 GS 11 Reserved

DP_INBAND_MODE: This 2-bit field indicates whether a current DP carriesin-band signaling information. An in-band signaling type is signaledaccording to the following Table 14.

TABLE 14 Value In-band mode 00 In-band signaling is not carried. 01INBAND-PLS is carried 10 INBAND-ISSY is carried 11 INBAND-PLS andINBAND-ISSY are carried

DP_PROTOCOL_TYPE: This 2-bit field indicates a protocol type of apayload carried by a given DP. The protocol type is signaled accordingto Table 15 below when input payload types are selected.

TABLE 15 If If If DP_PAY- DP_PAY- DP_PAY- LOAD_TYPE LOAD_TYPE LOAD_TYPEValue is TS is IP is GS 00 MPEG2-TS IPv4 (Note) 01 Reserved IPv6Reserved 10 Reserved Reserved Reserved 11 Reserved Reserved Reserved

DP_CRC_MODE: This 2-bit field indicates whether CRC encoding is used inan input formatting block. A CRC mode is signaled according to thefollowing Table 16.

TABLE 16 Value CRC mode 00 Not used 01 CRC-8 10 CRC-16 11 CRC-32

DNP_MODE: This 2-bit field indicates a null-packet deletion mode used byan associated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). DNP_MODE issignaled according to Table 17 below. If DP_PAYLOAD_TYPE is not TS(‘00’), DNP_MODE is set to a value of ‘00’.

TABLE 17 Value Null-packet deletion mode 00 Not used 01 DNP-NORMAL 10DNP-OFFSET 11 Reserved

ISSY_MODE: This 2-bit field indicates an ISSY mode used by an associatedDP when DP_PAYLOAD_TYPE is set to TS (‘00’). ISSY_MODE is signaledaccording to Table 18 below. If DP_PAYLOAD_TYPE is not TS (‘00’),ISSY_MODE is set to the value of ‘00’.

TABLE 18 Value ISSY mode 00 Not used 01 ISSY-UP 10 ISSY-BBF 11 Reserved

HC_MODE_TS: This 2-bit field indicates a TS header compression mode usedby an associated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). HC_MODE_TSis signaled according to the following Table 19.

TABLE 19 Value Header compression mode 00 HC_MODE_TS 1 01 HC_MODE_TS 210 HC_MODE_TS 3 11 HC_MODE_TS 4

HC_MODE_IP: This 2-bit field indicates an IP header compression modewhen DP_PAYLOAD_TYPE is set to IP (‘01’). HC_MODE_IP is signaledaccording to the following Table 20.

TABLE 20 Value Header compression mode 00 No compression 01 HC_MODE_IP 110 to 11 Reserved

PID: This 13-bit field indicates the PID number for TS headercompression when DP_PAYLOAD_TYPE is set to TS (‘00’) and HC_MODE_TS isset to ‘01’ or ‘10’.

RESERVED: This 8-bit field is reserved for future use.

The following fields appear only if FIC_FLAG is equal to ‘1’.

FIC_VERSION: This 8-bit field indicates the version number of the FIC.

FIC_LENGTH_BYTE: This 13-bit field indicates the length, in bytes, ofthe FIC.

RESERVED: This 8-bit field is reserved for future use.

The following fields appear only if AUX_FLAG is equal to ‘1’.

NUM_AUX: This 4-bit field indicates the number of auxiliary streams.Zero means no auxiliary stream is used.

AUX_CONFIG_RFU: This 8-bit field is reserved for future use.

AUX_STREAM_TYPE: This 4-bit is reserved for future use for indicating atype of a current auxiliary stream.

AUX_PRIVATE_CONFIG: This 28-bit field is reserved for future use forsignaling auxiliary streams.

FIG. 26 illustrates PLS2 data according to another embodiment of thepresent invention.

FIG. 26 illustrates PLS2-DYN data of the PLS2 data. Values of thePLS2-DYN data may change during the duration of one frame group whilesizes of fields remain constant.

Details of fields of the PLS2-DYN data are as below.

FRAME_INDEX: This 5-bit field indicates a frame index of a current framewithin a superframe. An index of a first frame of the superframe is setto ‘0’.

PLS_CHANGE_COUNTER: This 4-bit field indicates the number of superframesbefore a configuration changes. A next superframe with changes in theconfiguration is indicated by a value signaled within this field. Ifthis field is set to a value of ‘0000’, it means that no scheduledchange is foreseen. For example, a value of ‘1’ indicates that there isa change in the next superframe.

FIC_CHANGE_COUNTER: This 4-bit field indicates the number of superframesbefore a configuration (i.e., content of the FIC) changes. A nextsuperframe with changes in the configuration is indicated by a valuesignaled within this field. If this field is set to a value of ‘0000’,it means that no scheduled change is foreseen. For example, a value of‘0001’ indicates that there is a change in the next superframe.

RESERVED: This 16-bit field is reserved for future use.

The following fields appear in a loop over NUM_DP, which describeparameters associated with a DP carried in a current frame.

DP_ID: This 6-bit field uniquely indicates a DP within a PHY profile.

DP_START: This 15-bit (or 13-bit) field indicates a start position ofthe first of the DPs using a DPU addressing scheme. The DP_START fieldhas differing length according to the PHY profile and FFT size as shownin the following Table 21.

TABLE 21 DP_START field size PHY profile 64K 16K Base 13 bits 15 bitsHandheld — 13 bits Advanced 13 bits 15 its

DP_NUM_BLOCK: This 10-bit field indicates the number of FEC blocks in acurrent TI group for a current DP. A value of DP_NUM_BLOCK ranges from 0to 1023.

RESERVED: This 8-bit field is reserved for future use.

The following fields indicate FIC parameters associated with the EAC.

EAC_FLAG: This 1-bit field indicates the presence of the EAC in acurrent frame. This bit is the same value as EAC_FLAG in a preamble.

EAS_WAKE_UP_VERSION_NUM: This 8-bit field indicates a version number ofa wake-up indication.

If the EAC_FLAG field is equal to ‘1’, the following 12 bits areallocated to EAC_LENGTH_BYTE. If the EAC_FLAG field is equal to ‘0’, thefollowing 12 bits are allocated to EAC_COUNTER.

EAC_LENGTH_BYTE: This 12-bit field indicates a length, in bytes, of theEAC.

EAC_COUNTER: This 12-bit field indicates the number of frames before aframe where the EAC arrives.

The following fields appear only if the AUX_FLAG field is equal to ‘1’.

AUX_PRIVATE_DYN: This 48-bit field is reserved for future use forsignaling auxiliary streams. A meaning of this field depends on a valueof AUX_STREAM_TYPE in a configurable PLS2-STAT.

CRC_32: A 32-bit error detection code, which is applied to the entirePLS2.

FIG. 27 illustrates a logical structure of a frame according to anembodiment of the present invention.

As above mentioned, the PLS, EAC, FIC, DPs, auxiliary streams and dummycells are mapped to the active carriers of OFDM symbols in a frame. PLS1and PLS2 are first mapped to one or more FSSs. Thereafter, EAC cells, ifany, are mapped to an immediately following PLS field, followed next byFIC cells, if any. The DPs are mapped next after the PLS or after theEAC or the FIC, if any. Type 1 DPs are mapped first and Type 2 DPs aremapped next. Details of types of the DPs will be described later. Insome cases, DPs may carry some special data for EAS or service signalingdata. The auxiliary streams or streams, if any, follow the DPs, which inturn are followed by dummy cells. When the PLS, EAC, FIC, DPs, auxiliarystreams and dummy data cells are mapped all together in the abovementioned order, i.e. the PLS, EAC, FIC, DPs, auxiliary streams anddummy data cells, cell capacity in the frame is exactly filled.

FIG. 28 illustrates PLS mapping according to an embodiment of thepresent invention.

PLS cells are mapped to active carriers of FSS(s). Depending on thenumber of cells occupied by PLS, one or more symbols are designated asFSS(s), and the number of FSS(s) N_(FSS) is signaled by NUM_FSS in PLS1.The FSS is a special symbol for carrying PLS cells. Since robustness andlatency are critical issues in the PLS, the FSS(s) have higher pilotdensity, allowing fast synchronization and frequency-only interpolationwithin the FSS.

PLS cells are mapped to active carriers of the FSS(s) in a top-downmanner as shown in the figure. PLS1 cells are mapped first from a firstcell of a first FSS in increasing order of cell index. PLS2 cells followimmediately after a last cell of PLS1 and mapping continues downwarduntil a last cell index of the first FSS. If the total number ofrequired PLS cells exceeds the number of active carriers of one FSS,mapping proceeds to a next FSS and continues in exactly the same manneras the first FSS.

After PLS mapping is completed, DPs are carried next. If an EAC, an FICor both are present in a current frame, the EAC and the FIC are placedbetween the PLS and “normal” DPs.

Hereinafter, description will be given of encoding an FEC structureaccording to an embodiment of the present invention. As above mentioned,the data FEC encoder may perform FEC encoding on an input BBF togenerate an FECBLOCK procedure using outer coding (BCH), and innercoding (LDPC). The illustrated FEC structure corresponds to theFECBLOCK. In addition, the FECBLOCK and the FEC structure have samevalue corresponding to a length of an LDPC codeword.

As described above, BCH encoding is applied to each BBF (K_(bch) bits),and then LDPC encoding is applied to BCH-encoded BBF (K_(ldpc)bits=N_(bch) bits).

A value of N_(ldpc) is either 64,800 bits (long FECBLOCK) or 16,200 bits(short FECBLOCK).

Table 22 and Table 23 below show FEC encoding parameters for the longFECBLOCK and the short FECBLOCK, respectively.

TABLE 22 BCH error correction LDPC rate N_(ldpc) K_(ldpc) K_(bch)capability N_(bch) − K_(bch) 5/15 64800 21600 21408 12 192 6/15 2592025728 7/15 30240 30048 8/15 34560 34368 9/15 38880 38688 10/15  4320043008 11/15  47520 47328 12/15  51840 51648 13/15  56160 55968

TABLE 23 BCH error correction LDPC rate N_(ldpc) K_(ldpc) K_(bch)capability N_(bch) − K_(bch) 5/15 16200 5400 5232 12 168 6/15 6480 63127/15 7560 7392 8/15 8640 8472 9/15 9720 9552 10/15  10800 10632 11/15 11880 11712 12/15  12960 12792 13/15  14040 13872

Detailed operations of BCH encoding and LDPC encoding are as below.

A 12-error correcting BCH code is used for outer encoding of the BBF. ABCH generator polynomial for the short FECBLOCK and the long FECBLOCKare obtained by multiplying all polynomials together.

LDPC code is used to encode an output of outer BCH encoding. To generatea completed B_(ldpc) (FECBLOCK), P_(ldpc) (parity bits) is encodedsystematically from each I_(ldpc) (BCH—encoded BBF), and appended toI_(ldpc). The completed B_(ldpc) (FECBLOCK) is expressed by thefollowing Equation.B _(ldpc)=[I _(ldpc) P _(ldpc)]=[i ₀ ,i ₁ , . . . ,i _(K) _(ldpc) ₋₁ ,p₀ ,p ₁ , . . . ,p _(N) _(ldpc) _(-K) _(ldpc) ₋₁]   [Equation 2]

Parameters for the long FECBLOCK and the short FECBLOCK are given in theabove Tables 22 and 23, respectively.

A detailed procedure to calculate N_(ldpc)−K_(ldpc) parity bits for thelong FECBLOCK, is as follows.

1) Initialize the parity bitsp ₀ =p ₁ =p ₂ = . . . =p _(N) _(ldpc) _(-K) _(ldpc) ₋₁=0   [Equation 3]

2) Accumulate a first information bit—i₀, at a parity bit addressspecified in a first row of addresses of a parity check matrix. Detailsof the addresses of the parity check matrix will be described later. Forexample, for the rate of 13/15,p ₉₈₃ =p ₉₈₃ ⊕i ₀ p ₂₈₁₅ =p ₂₈₁₅ ⊕i ₀p ₄₈₃₇ =p ₄₈₃₇ ⊕i ₀ p ₄₉₈₉ =p ₄₉₈₉ ⊕i ₀p ₆₁₃₈ =p ₆₁₃₈ ⊕i ₀ p ₆₄₅₈ =p ₆₄₅₈ ⊕i ₀p ₆₉₂₁ =p ₆₉₂₁ ⊕i ₀ p ₆₉₇₄ =p ₆₉₇₄ ⊕i ₀p ₇₅₇₂ =p ₇₅₇₂ ⊕i ₀ p ₈₂₆₀ =p ₈₂₆₀ ⊕i ₀p ₈₄₉₆ =p ₈₄₉₆ ⊕i ₀   [Equation 4]

3) For the next 359 information bits, i_(s), s=1, 2, . . . , 359,accumulate i_(s) at parity bit addresses using following Equation.{x+(s mod 360)×Q _(ldpc)} mod(N _(ldpc) −K _(ldpc))   [Equation 5]

Here, x denotes an address of a parity bit accumulator corresponding toa first bit i₀, and Q_(ldpc) is a code rate dependent constant specifiedin the addresses of the parity check matrix. Continuing with theexample, Q_(ldpc)=24 for the rate of 13/15, so for an information biti₁, the following operations are performed.p ₁₀₀₇ =p ₁₀₀₇ ⊕i ₁ p ₂₃₈₉ =p ₂₈₃₉ ⊕i ₁p ₄₈₆₁ =p ₄₈₆₁ ⊕i ₁ p ₅₀₁₃ =p ₅₀₁₃ ⊕i ₁p ₆₁₆₂ =p ₆₁₆₂ ⊕i ₁ p ₆₄₈₂ =p ₆₄₈₂ ⊕i ₁p ₆₉₄₅ =p ₆₉₄₅ ⊕i ₁ p ₆₉₉₈ =p ₆₉₉₈ ⊕i ₁p ₇₅₉₆ =p ₇₅₉₆ ⊕i ₁ p ₈₂₈₄ =p ₈₂₈₄ ⊕i ₁p ₈₅₂₀ =p ₈₅₂₀ ⊕i ₁   [Equation 6]

4) For a 361th information bit i₃₆₀, an address of the parity bitaccumulator is given in a second row of the addresses of the paritycheck matrix. In a similar manner, addresses of the parity bitaccumulator for the following 359 information bits i_(s), s=361, 362, .. . , 719 are obtained using Equation 6, where x denotes an address ofthe parity bit accumulator corresponding to the information bit i₃₆₀,i.e., an entry in the second row of the addresses of the parity checkmatrix.

5) In a similar manner, for every group of 360 new information bits, anew row from the addresses of the parity check matrix is used to findthe address of the parity bit accumulator.

After all of the information bits are exhausted, a final parity bit isobtained as below.

6) Sequentially perform the following operations starting with i=1.p _(i) =p _(i) ⊕p _(i-1) ,i=1,2,. . . ,N _(ldpc) −K _(ldpc)−1  [Equation7]

Here, final content of p_(i) (i=0, 1, . . . , N_(ldpc)−K_(ldpc)−1) isequal to a parity bit p_(i).

TABLE 24 Code rate Q_(ldpc) 5/15 120 6/15 108 7/15 96 8/15 84 9/15 7210/15  60 11/15  48 12/15  36 13/15  24

This LDPC encoding procedure for the short FECBLOCK is in accordancewith t LDPC encoding procedure for the long FECBLOCK, except that Table24 is replaced with Table 25, and the addresses of the parity checkmatrix for the long FECBLOCK are replaced with the addresses of theparity check matrix for the short FECBLOCK.

TABLE 25 Code rate Q_(ldpc) 5/15 30 6/15 27 7/15 24 8/15 21 9/15 1810/15  15 11/15  12 12/15  9 13/15  6

FIG. 29 illustrates time interleaving according to an embodiment of thepresent invention.

(a) to (c) show examples of a TI mode.

A time interleaver operates at the DP level. Parameters of timeinterleaving (TI) may be set differently for each DP.

The following parameters, which appear in part of the PLS2-STAT data,configure the TI.

DP_TI_TYPE (allowed values: 0 or 1): This parameter represents the TImode. The value of ‘0’ indicates a mode with multiple TI blocks (morethan one TI block) per TI group. In this case, one TI group is directlymapped to one frame (no inter-frame interleaving). The value of ‘1’indicates a mode with only one TI block per TI group. In this case, theTI block may be spread over more than one frame (inter-frameinterleaving).

DP_TI_LENGTH: If DP_TI_TYPE=‘0’, this parameter is the number of TIblocks N_(TI) per TI group. For DP_TI_TYPE=‘1’, this parameter is thenumber of frames P_(I) spread from one TI group.

DP_NUM_BLOCK_MAX (allowed values: 0 to 1023): This parameter representsthe maximum number of XFECBLOCKs per TI group.

DP_FRAME_INTERVAL (allowed values: 1, 2, 4, and 8): This parameterrepresents the number of the frames I_(JUMP) between two successiveframes carrying the same DP of a given PHY profile.

DP_TI_BYPASS (allowed values: 0 or 1): If time interleaving is not usedfor a DP, this parameter is set to ‘1’. This parameter is set to ‘0’ iftime interleaving is used.

Additionally, the parameter DP_NUM_BLOCK from the PLS2-DYN data is usedto represent the number of XFECBLOCKs carried by one TI group of the DP.

When time interleaving is not used for a DP, the following TI group,time interleaving operation, and TI mode are not considered. However,the delay compensation block for the dynamic configuration informationfrom the scheduler may still be required. In each DP, the XFECBLOCKsreceived from SSD/MIMO encoding are grouped into TI groups. That is,each TI group is a set of an integer number of XFECBLOCKs and contains adynamically variable number of XFECBLOCKs. The number of XFECBLOCKs inthe TI group of index n is denoted by N_(xBLOCK_Group)(n) and issignaled as DP_NUM_BLOCK in the PLS2-DYN data. Note thatN_(xBLOCK_Group)(n) may vary from a minimum value of 0 to a maximumvalue of N_(xBLOCK_Group_MAX) (corresponding to DP_NUM_BLOCK_MAX), thelargest value of which is 1023.

Each TI group is either mapped directly to one frame or spread overP_(I) frames. Each TI group is also divided into more than one TI block(N_(TI)), where each TI block corresponds to one usage of a timeinterleaver memory. The TI blocks within the TI group may containslightly different numbers of XFECBLOCKs. If the TI group is dividedinto multiple TI blocks, the TI group is directly mapped to only oneframe. There are three options for time interleaving (except an extraoption of skipping time interleaving) as shown in the following Table26.

TABLE 26 Modes Descriptions Op- Each TI group contains one TI block andis mapped directly to tion 1 one frame as shown in (a). This option issignaled in PLS2- STAT by DP_TI_TYPE = ‘0’ and DP_TI_LENGTH = ‘1’(N_(TI) = 1). Op- Each TI group contains one TI block and is mapped tomore tion 2 than one frame. (b) shows an example, where one TI group ismapped to two frames, i.e., DP_TI_LENGTH = ‘2’ (P_(I) = 2) andDP_FRAME_INTERVAL (I_(JUMP) = 2). This provides greater time diversityfor low data-rate services. This option is signaled in PLS2-STAT byDP_TI_TYPE = ‘1’. Op- Each TI group is divided into multiple TI blocksand is mapped tion 3 directly to one frame as shown in (c). Each TIblock may use a full TI memory so as to provide a maximum bit-rate for aDP. This option is signaled in PLS2-STAT by DP_TI_TYPE = ‘0’ andDP_TI_LENGTH = N_(TI), while P_(I) = 1.

Typically, the time interleaver may also function as a buffer for DPdata prior to a process of frame building. This is achieved by means oftwo memory banks for each DP. A first TI block is written to a firstbank. A second TI block is written to a second bank while the first bankis being read from and so on.

The TI is a twisted row-column block interleaver. For an s^(th) TI blockof an n^(th) TI group, the number of rows N_(r) of a TI memory is equalto the number of cells N_(cells), i.e., N_(r)=N_(cells) while the numberof columns N_(c) is equal to the number N_(xBLOCK_TI)(n,s).

FIG. 30 illustrates a basic operation of a twisted row-column blockinterleaver according to an embodiment of the present invention.

FIG. 30(a) shows a write operation in the time interleaver and FIG.30(b) shows a read operation in the time interleaver. A first XFECBLOCKis written column-wise into a first column of a TI memory, and a secondXFECBLOCK is written into a next column, and so on as shown in (a).Then, in an interleaving array, cells are read diagonal-wise. Duringdiagonal-wise reading from a first row (rightwards along a row beginningwith a left-most column) to a last row, N_(r) cells are read out asshown in (b). In detail, assuming z_(n,s,i)(i=0, . . . , N_(r)N_(c)) asa TI memory cell position to be read sequentially, a reading process insuch an interleaving array is performed by calculating a row indexR_(n,s,i), a column index C_(n,s,i), and an associated twistingparameter T_(n,s,i) as in the following Equation.

$\begin{matrix}{{{GENERATE}\mspace{11mu}\left( {R_{n,s,i},C_{n,s,i,}} \right)} = \left\{ {{R_{n,s,i} = {{mod}\mspace{11mu}\left( {i,N_{r}} \right)}},{T_{n,s,i} = {{mod}\mspace{11mu}\left( {{S_{shift} \times R_{n,s,i}},N_{c}} \right)}},{C_{n,s,i} = {{mod}\mspace{11mu}\left( {{T_{n,s,i} + \left\lfloor \frac{i}{N_{r}} \right\rfloor},N_{c}} \right)}}} \right\}} & \left\lbrack {{Equation}\mspace{14mu} 8} \right\rbrack\end{matrix}$

Here, S_(shift) is a common shift value for a diagonal-wise readingprocess regardless of N_(xBLOCK_TI)(n,s), and the shift value isdetermined by N_(xBLOCK_TI_MAX) given in PLS2-STAT as in the followingEquation.

$\begin{matrix}{{for}\left\{ {\begin{matrix}{{N_{{xBLOCK}\;\_\;{TI}\;\_\;{MA}\; X}^{\prime} = {N_{{xBLOCK}\;\_\;{TI}\;\_\;{MA}\; X} + 1}},} & {{{if}\mspace{14mu} N_{{xBLOCK}\;\_\;{TI}\;\_\;{MA}\; X}{mod2}} = 0} \\{{N_{{xBLOCK}\;\_\;{TI}\;\_\;{MA}\; X}^{\prime} = N_{{xBLOCK}\;\_\;{TI}\;\_\;{MA}\; X}},} & {{{if}\mspace{14mu} N_{{xBLOCK}\;\_\;{TI}\;\_\;{MA}\; X}{mod2}} = 1}\end{matrix},{S_{shift} = \frac{N_{{xBLOCK}\;\_\;{TI}\;\_\;{MA}\; X}^{\prime} - 1}{2}}} \right.} & \left\lbrack {{Equation}\mspace{14mu} 9} \right\rbrack\end{matrix}$

As a result, cell positions to be read are calculated by coordinatesz_(n,s,i)=N_(r)C_(n,s,i)+R_(n,s,i).

FIG. 31 illustrates an operation of a twisted row-column blockinterleaver according to another embodiment of the present invention.

More specifically, FIG. 31 illustrates an interleaving array in a TImemory for each TI group, including virtual XFECBLOCKs whenN_(xBLOCK_TI)(0,0)=3, N_(xBLOCK_TI)(1,0)=6, and N_(xBLOCK_TI)(2,0)=5.

A variable number N_(xBLOCK_TI)(n,s)=N_(r) may be less than or equal toN_(xBLOCK_TI_MAX). Thus, in order to achieve single-memorydeinterleaving at a receiver side regardless of N_(xBLOCK_TI)(n,s), theinterleaving array for use in the twisted row-column block interleaveris set to a size of N_(r)×N_(c)=N_(cells)×N′_(xBLOCK_TI_MAX) byinserting the virtual XFECBLOCKs into the TI memory and a readingprocess is accomplished as in the following Equation.

[Equation 10] p = 0;  for i = 0;i < N_(cells)N_(xBLOCK) _(—) _(TI) _(—)_(MAX)′;i = i + 1  {GENERATE (R_(n,s,i),C_(n,s,i));  V_(i) =N_(r)C_(n,s,j) + R_(n,s,j)  if V_(i) < N_(cells)N_(xBLOCK) _(—)_(TI)(n,s)  {   Z_(n,s,p) = V_(i); p = p + 1;   }  }

The number of TI groups is set to 3. An option of the time interleaveris signaled in the PLS2-STAT data by DP_TI_TYPE=‘0’,DP_FRAME_INTERVAL=‘1’, and DP_TI_LENGTH=‘1’, i.e., NTI=1, IJUMP=1, andPI=1. The number of XFECBLOCKs, each of which has Ncells=30 cells, perTI group is signaled in the PLS2-DYN data by NxBLOCK_TI(0,0)=3,NxBLOCK_TI(1,0)=6, and NxBLOCK_TI(2,0)=5, respectively. A maximum numberof XFECBLOCKs is signaled in the PLS2-STAT data by NxBLOCK_Group_MAX,which leads to └N_(xBLOCK_Group_MAX)/N_(TI)┘=N_(xBLOCK_TI_MAX)=6.

The purpose of the Frequency Interleaver, which operates on datacorresponding to a single OFDM symbol, is to provide frequency diversityby randomly interleaving data cells received from the frame builder. Inorder to get maximum interleaving gain in a single frame, a differentinterleaving-sequence is used for every OFDM symbol pair comprised oftwo sequential OFDM symbols.

Therefore, the frequency interleaver according to the present embodimentmay include an interleaving address generator for generating aninterleaving address for applying corresponding data to a symbol pair.

FIG. 32 illustrates an interleaving address generator including a mainpseudo-random binary sequence (PRBS) generator and a sub-PRBS generatoraccording to each FFT mode according to an embodiment of the presentinvention.

(a) shows the block diagrams of the interleaving-address generator for8K FFT mode, (b) shows the block diagrams of the interleaving-addressgenerator for 16K FFT mode and (c) shows the block diagrams of theinterleaving-address generator for 32K FFT mode.

The interleaving process for the OFDM symbol pair is described asfollows, exploiting a single interleaving-sequence. First, availabledata cells (the output cells from the Cell Mapper) to be interleaved inone OFDM symbol O_(m,l) is defined as O_(m,i)=[x_(m,l,0), . . . ,x_(m,l,p), . . . , x_(m,l,N) _(data) ₋₁] for l=0, . . . , N_(sym)=1,where x_(m,l,p) is the p^(th) call of the l^(th) OFDM symbol in them^(th) frame and N_(data) is the number of data cells: N_(data)=C_(FSS)for the frame signaling symbol(s), N_(data)=C_(data) for the normaldata, and N_(data)=C_(FES) for the frame edge symbol. In addition, theinterleaved data cells are defined as P_(m,l)=[v_(m,l,0), . . . ,v_(m,l,N) _(data) ₋₁] for l=0, . . . , N_(sym)−1.

For the OFDM symbol pair, the interleaved OFDM symbol pair is given byv_(m,l,H) _(i) _((p))=x_(m,l,p), p=0, . . . , N_(data)−1, for the firstOFDM symbol of each pair v_(m,l,p)=x_(m,l,H) _(l) _((p)), p=0, . . . ,N_(data)−1, for the second OFDM symbol of each pair, where H_(l)(p) isthe interleaving

address generated by a PRBS generator.

FIG. 33 illustrates a main PRBS used for all FFT modes according to anembodiment of the present invention.

(a) illustrates the main PRBS, and (b) illustrates a parameter Nmax foreach FFT mode.

FIG. 34 illustrates a sub-PRBS used for FFT modes and an interleavingaddress for frequency interleaving according to an embodiment of thepresent invention.

(a) illustrates a sub-PRBS generator, and (b) illustrates aninterleaving address for frequency interleaving. A cyclic shift valueaccording to an embodiment of the present invention may be referred toas a symbol offset.

FIG. 35 illustrates a write operation of a time interleaver according toan embodiment of the present invention.

FIG. 35 illustrates a write operation for two TI groups.

A left block in the figure illustrates a TI memory address array, andright blocks in the figure illustrate a write operation when two virtualFEC blocks and one virtual FEC block are inserted into heads of twocontiguous TI groups, respectively.

Hereinafter, description will be given of a configuration of a timeinterleaver and a time interleaving method using both a convolutionalinterleaver (CI) and a block interleaver (BI) or selectively usingeither the CI or the BI according to a physical layer pipe (PLP) mode. APLP according to an embodiment of the present invention is a physicalpath corresponding to the same concept as that of the above-describedDP, and a name of the PLP may be changed by a designer.

A PLP mode according to an embodiment of the present invention mayinclude a single PLP mode or a multi-PLP mode according to the number ofPLPs processed by a broadcast signal transmitter or a broadcast signaltransmission apparatus. The single PLP mode corresponds to a case inwhich one PLP is processed by the broadcast signal transmissionapparatus. The single PLP mode may be referred to as a single PLP.

The multi-PLP mode corresponds to a case in which one or more PLPs areprocessed by the broadcast signal transmission apparatus. The multi-PLPmode may be referred to as multiple PLPs.

In the present invention, time interleaving in which different timeinterleaving schemes are applied according to PLP modes may be referredto as hybrid time interleaving. Hybrid time interleaving according to anembodiment of the present invention is applied for each PLP (or at eachPLP level) in the multi-PLP mode.

FIG. 36 illustrates an interleaving type applied according to the numberof PLPs in a table.

In a time interleaving according to an embodiment of the presentinvention, an interleaving type may be determined based on a value ofPLP_NUM. PLP_NUM is a signaling field indicating a PLP mode. WhenPLP_NUM has a value of 1, the PLP mode corresponds to a single PLP. Thesingle PLP according to the present embodiment may be applied only to aCI.

When PLP_NUM has a value greater than 1, the PLP mode corresponds tomultiple PLPs. The multiple PLPs according to the present embodiment maybe applied to the CI and a BI. In this case, the CI may performinter-frame interleaving, and the BI may perform intra-frameinterleaving.

FIG. 37 is a block diagram including a first example of a structure of ahybrid time interleaver described above.

The hybrid time interleaver according to the first example may include aBI and a CI. The time interleaver of the present invention may bepositioned between a BICM chain block and a frame builder.

The BICM chain block illustrated in FIGS. 37 and 38 may include theblocks in the processing block 5000 of the BICM block illustrated inFIG. 19 except for the time interleaver 5050. The frame builderillustrated in FIGS. 37 and 38 may perform the same function as that ofthe frame building block 1020 of FIG. 18.

As described in the foregoing, it is possible to determine whether toapply the BI according to the first example of the structure of thehybrid time interleaver depending on values of PLP_NUM. That is, whenPLP_NUM=1, the BI is not applied (BI is turned OFF) and only the CI isapplied. When PLP_NUM>1, both the BI and the CI may be applied (BI isturned ON). A structure and an operation of the CI applied whenPLP_NUM>1 may be the same as or similar to a structure and an operationof the CI applied when PLP_NUM=1.

FIG. 38 is a block diagram including a second example of the structureof the hybrid time interleaver described above.

An operation of each block included in the second example of thestructure of the hybrid time interleaver is the same as the abovedescription in FIG. 20. It is possible to determine whether to apply aBI according to the second example of the structure of the hybrid timeinterleaver depending on values of PLP_NUM. Each block of the hybridtime interleaver according to the second example may perform operationsaccording to embodiments of the present invention. In this instance, anapplied structure and operation of a CI may be different between a caseof PLP_NUM=1 and a case of PLP_NUM>1.

FIG. 39 is a block diagram including a first example of a structure of ahybrid time deinterleaver.

The hybrid time deinterleaver according to the first example may performan operation corresponding to a reverse operation of the hybrid timeinterleaver according to the first example described above. Therefore,the hybrid time deinterleaver according to the first example of FIG. 39may include a convolutional deinterleaver (CDI) and a blockdeinterleaver (BDI).

A structure and an operation of the CDI applied when PLP_NUM>1 may bethe same as or similar to a structure and an operation of the CDIapplied when PLP_NUM=1.

It is possible to determine whether to apply the BDI according to thefirst example of the structure of the hybrid time deinterleaverdepending on values of PLP_NUM. That is, when PLP_NUM=1, the BDI is notapplied (BDI is turned OFF) and only the CDI is applied.

The CDI of the hybrid time deinterleaver may perform inter-framedeinterleaving, and the BDEI may perform intra-frame deinterleaving.Details of inter-frame deinterleaving and intra-frame deinterleaving arethe same as the above description.

A BICM decoding block illustrated in FIGS. 39 and 40 may perform areverse operation of the BICM chain block of FIGS. 37 and 38.

FIG. 40 is a block diagram including a second example of the structureof the hybrid time deinterleaver.

The hybrid time deinterleaver according to the second example mayperform an operation corresponding to a reverse operation of the hybridtime interleaver according to the second example described above. Anoperation of each block included in the second example of the structureof the hybrid time deinterleaver may be the same as the abovedescription in FIG. 39.

It is possible to determine whether to apply a BDI according to thesecond example of the structure of the hybrid time deinterleaverdepending on values of PLP_NUM. Each block of the hybrid timedeinterleaver according to the second example may perform operationsaccording to embodiments of the present invention. In this instance, anapplied structure and operation of a CDI may be different between a caseof PLP_NUM=1 and a case of PLP_NUM>1.

FIG. 41 is a block diagram illustrating a hybrid broadcast receptionapparatus according to an embodiment of the present invention. A hybridbroadcast system can transmit broadcast signals in connection withterrestrial broadcast networks and the Internet. The hybrid broadcastreception apparatus can receive broadcast signals through terrestrialbroadcast networks (broadcast networks) and the Internet (broadband).The hybrid broadcast reception apparatus may include physical layermodule(s), physical layer I/F module(s), service/content acquisitioncontroller, Internet access control module(s), a signaling decoder, aservice signaling manager, a service guide manager, an applicationsignaling manager, an alert signal manager, an alert signaling parser, atargeting signaling parser, a streaming media engine, a non-real timefile processor, a component synchronizer, a targeting processor, anapplication processor, an A/V processor, a device manager, a datasharing and communication unit, redistribution module(s), companiondevice(s) and/or an external management module.

The physical layer module(s) can receive a broadcast related signalthrough a terrestrial broadcast channel, process the received signal,convert the processed signal into an appropriate format and deliver thesignal to the physical layer I/F module(s).

The physical layer I/F module(s) can acquire an IP datagram frominformation obtained from the physical layer module. In addition, thephysical layer I/F module can convert the acquired IP datagram into aspecific frame (e.g., RS frame, GSE, etc.).

The service/content acquisition controller can perform control operationfor acquisition of services, content and signaling data related theretothrough broadcast channels and/or broadband channels.

The Internet access control module(s) can control receiver operationsfor acquiring service, content, etc. through broadband channels.

The signaling decoder can decode signaling information acquired throughbroadcast channels.

The service signaling manager can extract signaling information relatedto service scan and/or content from the IP datagram, parse the extractedsignaling information and manage the signaling information.

The service guide manager can extract announcement information from theIP datagram, manage a service guide (SG) database and provide a serviceguide.

The application signaling manager can extract signaling informationrelated to application acquisition from the IP datagram, parse thesignaling information and manage the signaling information.

The alert signaling parser can extract signaling information related toalerting from the IP datagram, parse the extracted signaling informationand manage the signaling information.

The targeting signaling parser can extract signaling information relatedto service/content personalization or targeting from the IP datagram,parse the extracted signaling information and manage the signalinginformation. In addition, the targeting signaling parser can deliver theparsed signaling information to the targeting processor.

The streaming media engine can extract audio/video data for A/Vstreaming from the IP datagram and decode the audio/video data.

The non-real time file processor can extract NRT data and file type datasuch as applications, decode and manage the extracted data.

The component synchronizer can synchronize content and services such asstreaming audio/video data and NRT data.

The targeting processor can process operations related toservice/content personalization on the basis of the targeting signalingdata received from the targeting signaling parser.

The application processor can process application related informationand downloaded application state and represent parameters.

The A/V processor can perform audio/video rendering related operationson the basis of decoded audio/video data and application data.

The device manager can perform connection and data exchange withexternal devices. In addition, the device manager can perform operationsof managing external devices connectable thereto, such asaddition/deletion/update of the external devices.

The data sharing and communication unit can process information relatedto data transmission and exchange between a hybrid broadcast receiverand external devices. Here, data that can be transmitted and exchangedbetween the hybrid broadcast receiver and external devices may besignaling data, A/V data and the like.

The redistribution module(s) can acquire information related to futurebroadcast services and content when the broadcast receiver cannotdirectly receive terrestrial broadcast signals. In addition, theredistribution module can support acquisition of future broadcastservices and content by future broadcast systems when the broadcastreceiver cannot directly receive terrestrial broadcast signals.

The companion device(s) can share audio, video or signaling data bybeing connected to the broadcast receiver according to the presentinvention. The companion device may be an external device connected tothe broadcast receiver.

The external management module can refer to a module for broadcastservices/content provision. For example, the external management modulecan be a future broadcast services/content server. The externalmanagement module may be an external device connected to the broadcastreceiver.

FIG. 42 is a block diagram illustrating a hybrid broadcast receiveraccording to an embodiment of the present invention.

The hybrid broadcast receiver can receive hybrid broadcast servicesthrough interworking of terrestrial broadcasting and a broadband networkin DTV services of a future broadcast system. The hybrid broadcastreceiver can receive broadcast audio/video (A/V) content transmittedthrough terrestrial broadcasting and receive enhancement data relatedthereto or part of broadcast A/V content through the broadband networkin real time. In the specification, the broadcast A/V content can bereferred to as media content.

The hybrid broadcast receiver may include a physical layer controllerD55010, a tuner D55020, a physical frame parser D55030, a link layerframe parser D55040, an IP/UDP datagram filter D55050, an ATSC 3.0digital TV (DTV) control engine D55060, an ALC/LCT+ client D55070, atiming controller D55080, a signaling parser D55090, a dynamic adaptivestreaming over HTTP (DASH) client D55100, an HTTP access client D55110,an ISO base media file format (BMFF) parser D55120 and/or a mediadecoder D55130.

The physical layer controller D55010 can control operations of the tunerD55020 and the physical frame parser D55030 using radio frequency (RF)information of a terrestrial broadcast channel that the hybrid broadcastreceiver intends to receive.

The tuner D55020 can receive a broadcast related signal through aterrestrial broadcast channel, process the received signal and convertthe signal into an appropriate format. For example, the tuner D55020 canconvert a received terrestrial broadcast signal into physical frames.

The physical frame parser D55030 can parse a received physical frame andacquire a link layer frame through processing related thereto.

The link layer parser D55040 can execute related operations foracquisition of link layer signaling or an IP/UDP datagram from the linklayer frame. The link layer parser D55040 can output at least one IP/UDPdatagram.

The IP/UDP datagram filter D55050 can filter a specific IP/UDP datagramfrom the received at least one IP/UDP datagram. That is, the IP/UDPdatagram filter D55050 can selectively filter an IP/UDP datagram, whichis selected by the ATSC 3.0 DTV control engine, from the at least oneIP/UDP datagram output from the link layer parser D55040. The IP/UDPdatagram filter D55050 can output an application layer transportprotocol packet such as ALC/LCT+.

The ATSC 3.0 DTV control engine D55060 can serve as an interface betweenmodules included in the hybrid broadcast receiver. In addition, the ATSC3.0 DTV control engine D55060 can deliver parameters necessary for eachmodule to each module and control operation of each module through theparameters. In the present invention, the ATSC 3.0 DTV control engineD55060 can transfer media presentation description (MPD) and/or an MPDURL to the DASH client D55100. In addition, the ATSC 3.0 DTV controlengine D55060 can transfer a delivery mode and/or a transport sessionidentifier (TSI) to the ALC/LCT+ client D55070. Here, the TSI indicatesan identifier of a session in which a transport packet including asignaling message such as MPD or MPD URL related signaling istransmitted, for example, ALC/LCT+ session corresponding to applicationlayer transport protocol or FLUTE session. In addition, the TSI cancorrespond to an asset ID of an MMT.

The ALC/LCT+ client D55070 can generate one or more ISO base media fileformat (ISO MMFF) objects by processing an application layer transportprotocol packet such as ALC/LCT+ and collecting and processing aplurality of packets. The application layer transport protocol packetmay include an ALC/LCT packet, an ALC/LCT+ packet, a ROUTE packet and/oran MMTP packet.

The timing controller D55080 can process a packet including system timeinformation and control a system clock according thereto.

The signaling parser D55090 can acquire and parse DTV broadcast servicerelated signaling, and generate and manage a channel map on the basis ofthe parsed signaling. In the present invention, the signaling parser canparse MPD or MPD related information extended from signalinginformation.

The DASH client D55100 can execute operations related to real-timestreaming or adaptive streaming. The DASH client D55100 can receive DASHcontent from an HTTP server through the HTTP access client D55110. TheDASH client D55100 can process a received DASH segment and output an ISOBMFF object. In the present invention, the DASH client D55100 candeliver a fully qualified representation ID or a segment URL to the ATSC3.0 DTV control engine D55060. Here, the fully qualified representationID can refer to an ID corresponding to a combination of an MPD URL,period@id and represenstation@id, for example. In addition, the DASHclient D55100 can receive the MPD or MPD URL from the ATSC 3.0 DTVcontrol engine D55060. The DASH client D55100 can receive a desiredmedia stream or DASH segment from the HTTP server using the received MPDor MPD URL. In the specification, the DASH client D55100 may be referredto as a processor.

The HTTP access client D55110 can request that the HTTP server providespecific information, receive a response to the request from the HTTPserver and process the response. Here, the HTTP server can process therequest received from the HTTP access client and provide a response tothe request.

The ISO BMFF parser D55120 can extract audio/video data from the ISOBMFF object.

The media decoder D55130 can decode the received audio/video data andperform processing for presentation of the decoded audio/video data.

To provide hybrid broadcast services through interworking of aterrestrial broadcast network and a broadband network according to thehybrid broadcast receiver of the present invention, MPD needs to beextended or modified. The aforementioned terrestrial broadcast systemcan transmit extended or modified MPD and the hybrid broadcast receivercan receive content through broadcasting or a broadband network usingthe extended or modified MPD. That is, the hybrid broadcast receiver canreceive the extended or modified MPD through terrestrial broadcastingand receive content through terrestrial broadcasting or a broadbandnetwork on the basis of the MPD. A description will be given of elementsor attributes that need to be additionally included in the extended ormodified MPD, compared to the conventional MPD. In the following, theextended or modified MPD is referred to as MPD.

The MPD can be extended or modified to represent ATSC 3.0 service. Theextended or modified MPD can additionally include MPD @anchorPresentationTime, Common@presentable, Common.Targeting,Common.TargetDevice and/or Common@associatedTo.

MPD@anchorPresentationTime can indicate presentation time anchor ofsegments included in the MPD, that is, base time. In the following,MPD@anchorPresentationTime can be used as effective time of the MPD.MPD@anchorPresentationTime can indicate the earliest playback time fromamong segments included in the MPD.

The MPD may further include common attributes and elements. The commonattributes and elements can be applied to AdaptionSet and Representationin the MPD. Common@presentable can indicate that media described by theMPD is a presentable component.

Common.Targeting can indicate targeting properties and/orpersonalization properties of the media described by the MPD.

Common.TargetDevice can indicate a target device or target devices ofthe media described by the MPD.

Common@ associatedTo can indicate adaptationSet and/or representationrelated to the media described by the MPD.

In addition, MPD@id, Period@id and AdaptationSet@id included in the MPDmay be necessary to specify media content described by the MPD. That is,the DASH client can specify content to be received on the basis of theMPD using MPD@id, Period@id and AdaptationSet@id and signal the contentto the ATSC 3.0 DTV control engine. The ATSC 3.0 DTV control engine canreceive the corresponding content and deliver the content to the DASHclient.

FIG. 43 illustrates a protocol stack of a future hybrid broadcast systemaccording to an embodiment of the present invention. As shown in thefigure, a future broadcast transmission system supporting IP basedhybrid broadcasting can encapsulate audio or video data of broadcastservices in the ISO base media file format (BMFF). Here, a DASH segmentor a media processing unit (MPU) of an MMT can be used forencapsulation. In addition, the future broadcast system can equallytransmit the encapsulated data through a broadcast network and theInternet or differently transmit the encapsulated data through thebroadcast network and the Internet according to attributes of therespective networks. Furthermore, the future broadcast system canequally transmit the encapsulated data using at least one of broadcastor broadband. In the case of a broadcast network using broadcast, thebroadcast system can transmit data encapsulated in the ISO BMFF throughan application layer transport protocol packet which supports real-timeobject transmission. For example, the broadcast system can encapsulatedata in a real-time object delivery over unidirectional transport(ROUTE) or MMTP transport packet. The broadcast system can process theencapsulated data into an IP/UDP datagram, load the IP/UDP datagram in abroadcast signal and transmit the broadcast signal. When broadband isused, the broadcast system can deliver the encapsulated data to areceiving side through streaming such as DASH.

In addition, the broadcast system can transmit broadcast servicesignaling information as follows. In the case of a broadcast networkusing broadcast, the broadcast system can transmit signaling informationthrough physical layers of the future broadcast transmission system andthe broadcast network according to signaling attributes. Here, thebroadcast system can transmit the signaling information through aspecific data pipe (DP) of a transport frame included in a broadcastsignal. Signaling information transmitted through broadcast may have aform of being encapsulated in a bitstream or IP/UDP datagram. Whenbroadband is used, the broadcast system can return and deliver signalingdata to a receiver in response to a request of the receiver.

In addition, the broadcast system can transmit broadcast service ESG orNRT content through the following method. In the case of a broadcastnetwork using broadcast, the broadcast system can encapsulate the ESG orNRT content in an application layer transport protocol packet, forexample, real-time object delivery over unidirectional transport (ROUTE)or MMTP transport packet. The broadcast system can generate an IP/UDPdatagram with the encapsulated ESG or NRT content, load the IP/UDPdatagram in a broadcast signal and transmit the broadcast signal. Whenbroadband is used, the broadcast system can return and deliver the ESGor NRT content to a receiver in response to a request of the receiver.

FIG. 44 illustrates a structure of a transport frame delivered to aphysical layer of the future broadcast transmission system according toan embodiment of the present invention. The future broadcast system cantransmit a transport frame using broadcast. In the figure, P1 located atthe front of the transport frame can refer to a symbol includinginformation for transport signal detection. P1 can include tuninginformation and a receiver can decode a part L1 following P1 on thebasis of a parameter included in the symbol P1. The broadcast system caninclude, in the part L1, information about transport frame configurationand characteristics of data pipes. That is, the receiver can obtain theinformation about the transport frame configuration and characteristicsof data pipes by decoding the part L1. In addition, the receiver canacquire information that needs to be shared between DPs through a commonDP. According to an embodiment, the transport frame may not include thecommon DP.

Components such as audio, video and data in the transport frame areincluded in an interleaved DP region composed of DP1 to DPn andtransmitted. Here, DPs through which components constituting eachservice (channel) are transmitted can be signaled through L1 or a commonPLP.

In addition, the future broadcast system can transmit information forrapidly acquiring information about services included in a transportframe. That is, the future broadcast system enables a future broadcastreceiver to rapidly acquire broadcast services and content relatedinformation included in a transport frame. When services/contentgenerated by one or more broadcasting stations are present in thecorresponding frame, the future broadcast system can enable the receiverto efficiently recognize the services/content according to thebroadcasting stations. That is, the future broadcast system can include,in a transport stream, service list information about services includedin the transport stream, and transmit the transport stream including theservice list information.

When an additional channel, for example, a fast information channel(FIC) is present, the broadcast system can transmit broadcast servicerelated information through the additional channel such that thereceiver can rapidly scan broadcast services and content in acorresponding frequency. As shown in FIG. 44, the broadcast system caninclude, in the transport stream, information for broadcast service scanand acquisition and transmit the same. Here, the region including theinformation for broadcast service scan and acquisition may be referredto as an FIC. The receiver can acquire information about broadcastservices generated and transmitted by one or more broadcasting stationsand easily and rapidly scan broadcast services available therein usingthe information.

In addition, a specific DP included in the transport stream can serve asa base DP capable of rapidly and robustly delivering signaling aboutbroadcast services and content transmitted in the correspondingtransport frame. Data transmitted through each DP of the transport frameof the physical layer is as shown in the lower part of FIG. 44. That is,link layer signaling or an IP datagram can be encapsulated in a genericpacket in a specific format and then transmitted through a DP. Here, theIP datagram can include signaling data. Link (low) layer signaling caninclude signaling related to fast service scan/acquisition, contextinformation of IP header compression and emergency alert.

FIG. 45 illustrates a transport packet of an application layer transportprotocol according to an embodiment of the present invention. Anapplication layer transport session can be composed of a combination ofan IP address and a port number. When the application layer transportprotocol corresponds to ROUTE, a ROUTE session can be composed of one ormore layered coding transport (LCT) sessions. For example, when a singlemedia component (e.g., DASH representation) is delivered through asingle LCT transport session, one or more media components can bemultiplexed and delivered through a single application transportsession. Furthermore, one or more transport objects can be deliveredthrough a single LCT transport session, and each transport object can bea DASH segment associated with DASH representation delivered through thetransport session.

For example, when the application layer transport protocol is an LCTbased protocol, a transport packet can be configured as follows. Thetransport packet can include an LCT header, a ROUTE header and payloaddata. A plurality of fields included in the transport packet is asfollows.

The LCT header can include the following fields. A version field V canindicate version information of the corresponding transport protocolpacket. A field C can include a flag related to the length of acongestion control information field which will be described below. Afield PSI can indicate protocol-specific information, that is,information specific to the corresponding protocol. A field S canindicate a flag associated with the length of a transport sessionidentifier (TSI) field. A field O can indicate a flag associated withthe length of a transport object identifier (TOI) field. A field H canindicate whether a half-word (16 bits) is added to the lengths of theTSI field and the TOI field. A field A (close session flag) can indicatethat a session is closed or closure of the session is imminent. A fieldB (close object flag) can indicate that an object being transmitted isclosed or closure of the object is imminent. A code point field canindicate information related to encoding or decoding of a payload of thecorresponding packet. For example, payload type can correspond to theinformation. A congestion control information field can indicateinformation related to congestion control. For example, the informationrelated to congestion control can be a current time slot index (CTSI), achannel number or a packet sequence number in the corresponding channelA transport session identifier field can indicate a transport fieldidentifier. A transport object identifier field can indicate anidentifier of an object transmitted through the corresponding transportsession.

A ROUTE (ALC) header can include additional information of the precedingLCT header, such as a payload identifier related to a forward errorcorrection scheme.

Payload data can indicate a data part of the payload of thecorresponding packet.

FIG. 46 illustrates a method for transmitting signaling data by thefuture broadcast system according to an embodiment of the presentinvention. Signaling data of the future broadcast system can betransmitted as shown in the figure. To enable the receiver to supportfast service/content scan and acquisition, the future broadcasttransmission system can transmit signaling data with respect to abroadcast service delivered through a corresponding physical layerframe, via a fast information channel (FIC). In the specification, theFIC can refer to information about a service list. Unless an additionalFIC is present, the signaling data may be delivered through a paththrough which link layer signaling is delivered. That is, signalinginformation including information about services and components (audioand video) thereof can be encapsulated in an IP/UDP datagram andtransmitted through one or more DPs in the physical layer frame.According to an embodiment, signaling information about services andservice components can be encapsulated in an application layer transportpacket (e.g. a ROUTE packet or an MMTP packet) and transmitted.

The upper part of FIG. 46 illustrates an example of delivering theaforementioned signaling data through an FIC or one or more DPs. Thatis, signaling data for supporting fast service scan/acquisition can bedelivered through the FIC and signaling data including detailedinformation about services can be encapsulated in an IP datagram andtransmitted through a specific DP. In the specification, the signalingdata including detailed information about services may be referred to asservice layer signaling.

The middle part of FIG. 46 illustrates an example of delivering theaforementioned signaling data through an FIC and one or more DPs. Thatis, signaling data for supporting fast service scan/acquisition can bedelivered through the FIC and signaling data including detailedinformation about services can be encapsulated in an IP datagram andtransmitted through a specific DP. In addition, part of signaling dataincluding information about a specific component included in a servicemay be delivered through one or more transport sessions in theapplication layer transport protocol. For example, part of the signalingdata can be delivered through one or more transport sessions in a ROUTEsession.

The lower part of FIG. 46 illustrates an example of delivering theaforementioned signaling data through an FIC and one or more DPs. Thatis, signaling data for supporting fast service scan/acquisition can bedelivered through the FIC and signaling data including detailedinformation about services can be delivered through one or more sessionsin a ROUTE session.

FIG. 47 is a table showing signaling data transmitted, by the futurebroadcast system according to an embodiment of the present invention,for fast broadcast service scan of a receiver. The specificationproposes signaling information for allowing a future broadcast receptionapparatus to scan and acquire broadcast services. In the futurebroadcast system, broadcast services and content generated by one ormore broadcasting stations can be transmitted within a specificfrequency. The receiver can use the aforementioned signaling informationto rapidly and easily scan broadcasting stations and services/contentsthereof, included in the corresponding frequency. The signalinginformation can be represented by the illustrated syntax and expressedin other formats such as XML.

The signaling information for fast service scan and acquisition can bedelivered to a fast information channel (FIC) corresponding to anadditional channel in a physical layer transport frame. Furthermore, theaforementioned signaling information may be delivered through a commonDP capable of carrying information that can be shared between data pipesof the physical layer. The signaling information may be deliveredthrough a path through which link layer signaling is transmitted. Thesignaling information may be encapsulated in an IP datagram anddelivered through a specific DP. Furthermore, the signaling informationmay be delivered via a service signaling channel through which servicesignaling is transmitted or a transport session of an application layer.

The signaling information (FIC information) for fast service scan andacquisition can include at least one of the following fields. In thespecification, the FIC information can be referred to as serviceacquisition information. An FIC_portocol_version field can indicate theversion of the structure of the signaling information. A TSID field canindicate an identifier of the overall broadcast stream. AnFIC_data_version field can indicate the data version of the FICinformation. The value of the FIC_data_version field can increase whenthe FIC is changed. A num_partitions field can indicate the number ofpartitions of a broadcast stream. To use the num_partitions field, it isassumed that each broadcast stream can be segmented into one or morepartitions and transmitted. Each partition can include a plurality ofDPs of a single broadcaster. Each partition can indicate a part of abroadcast stream used by a single broadcaster. Apartition_protocol_version field can indicate the version of theaforementioned partition structure. A base_DP_ID field can indicate theidentifier of a base DP of the corresponding partition. The base DP caninclude a service signaling table. The service signaling table caninclude a list of all services in the corresponding partition. That is,the service signaling table can list transmitted services. In addition,the service signaling table can define basic attributes of each service.The base DP may be a robust DP in the corresponding partition and mayinclude another signaling table with respect to the correspondingpartition. A base_DP_version field can indicate version informationrepresenting change of data transmitted through the base DP. Forexample, when serving signaling information is delivered through thebase DP, the base_DP_version field can increase by 1 if the servingsignaling information is changed. A num_services field can indicate thenumber of one or more components belonging to the correspondingpartition. A service_id field can indicate a service identifier. Achannel_number field can indicate a channel number associated with thecorresponding service. A service_category field can indicate thecategory of the corresponding service. For example, the service_categoryfield can indicate A/V, audio, ESG, CoD, etc. Ashort_service_name_length field can indicate the length of the name ofthe corresponding service. A short_Service_name field can indicate thename of the corresponding service. A service_status field can indicatethe status of the corresponding service. The service_status field canindicate an “active”, “suspended”, “hidden” or “shown” attribute. Aservice_distribution field can have an attribute similar to“multi-ensemble” flag of the ATSC M/H document. For example, theservice_distribution field can indicate information about whether thecorresponding service is included in the corresponding partition, theservice is presentable only with the corresponding partition althoughthe service is partially included in the partition, another partition isnecessary for presentation, or other broadcast streams are necessary forpresentation. An sp_indicator field is a service protection flag and canindicate whether one or more components necessary for presentation areprotected.

FIG. 48 is a table showing signaling data transmitted, by the futurebroadcast system according to an embodiment of the present invention,for fast broadcast service scan of a receiver. The FIC information(service acquisition information) for supporting fast broadcast servicescan and service/component acquisition can include information about anapplication layer transport session for delivering service and componentdata. As illustrated, the FIC information can be represented in a binaryformat. However, the FIC information may be represented in other formatssuch as XML according to embodiments. The FIC information can includethe following fields. An FIC_portocol_version field can indicate theversion of the structure of the signaling information. A TSID field canindicate an identifier of the overall broadcast stream. AnFIC_data_version field can indicate the data version of the FICinformation. The value of the FIC_data_version field can increase whenthe FIC is changed. A num_partitions field can indicate the number ofpartitions of a broadcast stream. To use the num_partitions field, it isassumed that each broadcast stream can be segmented into one or morepartitions and transmitted. Each partition can include a plurality ofDPs of a single broadcaster. Each partition can indicate a part of abroadcast stream used by a single broadcaster. A partition_id field canindicate the identifier of the corresponding partition. Apartition_protocol_version field can indicate the version of theaforementioned partition structure. A num_services field can indicatethe number of one or more components belonging to the correspondingpartition. A service_id field can indicate a service identifier. Aservice_data_version field can indicate a change of service loop data inthe FIC or a change of serving signaling data related to thecorresponding service. The value of the service_data_version field canincrease by 1 whenever included service data is changed. The receivercan detect data change in a service loop of the FIC or change ofsignaling related to the corresponding service using theservice_data_version field. A channel_number field can indicate achannel number associated with the corresponding service. Aservice_category field can indicate the category of the correspondingservice. For example, the service_category field can indicate A/V,audio, ESG, CoD, etc. A short_service_name_length field can indicate thelength of the name of the corresponding service. A short_Service_namefield can indicate the name of the corresponding service. Aservice_status field can indicate the status of the correspondingservice. The service_status field can indicate an attribute “active”,“suspended”, “hidden” or “shown”. A service_distribution field can havean attribute similar to the “multi-ensemble” flag of the ATSC M/Hdocument. For example, the service_distribution field can indicateinformation about whether the corresponding service is included in thecorresponding partition, the service is presentable only with thecorresponding partition although the service is partially included inthe partition, another partition is necessary for presentation, or otherbroadcast streams are necessary for presentation. An sp_indicator fieldis a service protection flag and can indicate whether one or morecomponents necessary for presentation are protected. An IP_version_flagfield can indicate the following IP address format. The IP_version_flagfield can indicate that IPv4 is used when the value thereof is 0 andindicate that IPv6 is used when the value thereof is 1. Asource_IP_address_flag field can indicate whether the FIC informationincludes source_IP_addr. The source_IP_address_flag field can indicatepresence of source_IP_addr when the value thereof is 1. Anum_transport_session field can indicate the number of transportsessions (e.g. ROUTE or MMTP sessions) in which component data of thecorresponding service is transmitted in a broadcast stream. Asource_IP_addr field can indicate the source IP address of an IPdatagram including the component data of the corresponding service whenthe source_IP_address_flag is 1. A dest_IP_addr field can indicate thedestination IP address of the IP datagram including the component dataof the corresponding service. A dest_UDP_port field can indicate the UDPport number of the IP datagram including the component data of thecorresponding service. An LSID_DP field can indicate the identifier of adata pipe of a physical layer, which delivers signaling includingdetailed information about a transport session. In the case of ROUTE,for example, the signaling including the detailed information about thetransport session can be an LCT session instance description includinginformation about an LCT transport session of a ROUTE session. Aservice_signaling_flag field can indicate whether service signaling istransmitted through the corresponding transport session. Theservice_signaling_flag field can indicate that data transmitted throughthe corresponding transport session (e.g. ROUTE or MMTP session)includes the service signaling when the value thereof is 1. A transportsession descriptors field can include transport session leveldescriptors. Each descriptor can be extended and include anum_descriptors field. Each descriptor can include as many descriptorloops as a number corresponding to a value indicated by thenum_descriptors field. The transport session descriptors field caninclude transport session level descriptors. A service descriptors fieldcan include service level descriptors. A partition descriptors field caninclude a partition level descriptor, and one partition can indicatepart of broadcast streams used by a single broadcaster. An FIC sessiondescriptors field can include FIC level descriptors. According to anembodiment, the fields included in the FIC may be included in a tableother than the FIC and transmitted along with a broadcast signal.

FIG. 49 illustrates a method for transmitting FIC based signalingaccording to an embodiment of the present invention. The aforementionedexample of delivering FIC based signaling is shown in the figure. In thespecification, FIC based signaling can be referred to as serviceacquisition information or service acquisition signaling. As shown inthe figure, physical layer signaling can include a field with respect tothe service acquisition information. The field with respect to theservice acquisition information can indicate whether the serviceacquisition information FIC is parsed to the receiver. The receiver cancheck whether service signaling data has been changed throughservice_data_version information by parsing the service acquisitioninformation. When the service signaling data has been changed, thebroadcast signal receiver can confirm a data pipe identifier of thephysical layer which delivers signaling including detailed informationabout the corresponding transport session, using an LSID_DP field. Thebroadcast receiver can confirm detailed information about the transportsession by parsing a DP indicated by the DP identifier. That is, thesignaling method of the future broadcast system can include a sequenceof confirming detailed information about the transport session bysignaling whether the service acquisition information is parsed throughthe physical layer signaling and signaling the position of the detailedinformation about the transmission session through the serviceacquisition information. Here, the detailed information about thetransport session can include an MPD transport table, an applicationsignaling table, a transport session descriptor (LSID) and/or acomponent mapping table (CMT).

FIG. 50 illustrates signaling data transmitted, by the future broadcastsystem according to an embodiment, for fast broadcast service scan of areceiver. The FIC information (service acquisition information) forsupporting fast broadcast service scan and service/component acquisitioncan include information about an application layer transport session fordelivering service and component data. As illustrated, the FICinformation can be represented in a binary format. However, the FICinformation may be represented in other formats such as XML according toembodiments. The FIC information can include the following fields. AnFIC_portocol_version field can indicate the version of the structure ofthe signaling information. A TSID field can indicate an identifier ofthe overall broadcast stream. An FIC_data_version field can indicate thedata version of the FIC information. The value of the FIC_data_versionfield can increase when the FIC is changed. A num_partitions field canindicate the number of partitions of a broadcast stream. To use thenum_partitions field, it is assumed that each broadcast stream can besegmented into one or more partitions and transmitted. Each partitioncan include a plurality of DPs of a single broadcaster. Each partitioncan indicate a part of a broadcast stream used by a single broadcaster.A partition_id field can indicate the identifier of the correspondingpartition. A partition_protocol_version field can indicate the versionof the aforementioned partition structure. A num_services field canindicate the number of one or more components belonging to thecorresponding partition. A service_id field can indicate a serviceidentifier. A service_data_version field can indicate a change ofservice loop data in the FIC or a change of serving signaling datarelated to the corresponding service. The value of theservice_data_version field can increase by 1 whenever included servicedata is changed. The receiver can detect data change in a service loopof the FIC or change of signaling related to the corresponding serviceusing the service_data_version field. A channel_number field canindicate a channel number associated with the corresponding service. Aservice_category field can indicate the category of the correspondingservice. For example, the service_category field can indicate A/V,audio, ESG, CoD, etc. A short_service_name_length field can indicate thelength of the name of the corresponding service. A short_Service_namefield can indicate the name of the corresponding service. Aservice_status field can indicate the status of the correspondingservice. The service_status field can indicate an “active”, “suspended”,“hidden” or “shown” attribute. A service_distribution field can have anattribute similar to “multi-ensemble” flag of the ATSC M/H document. Forexample, the service_distribution field can indicate information aboutwhether the corresponding service is included in the correspondingpartition, whether the service is presentable only with thecorresponding partition although the service is partially included inthe partition, whether another partition is necessary for presentation,or whether other broadcast streams are necessary for presentation. Ansp_indicator field is a service protection flag and can indicate whetherone or more components necessary for presentation are protected. AnIP_version_flag field can indicate the following IP address format. TheIP_version_flag field can indicate that IPv4 is used when the valuethereof is 0 and indicate that IPv6 is used when the value thereof is 1.A source_IP_address_flag field can indicate whether the FIC informationincludes source_IP_addr. The source_IP_address_flag field can indicatepresence of source_IP_addr when the value thereof is 1. Anum_transport_session field can indicate the number of transportsessions (e.g. ROUTE or MMTP sessions) in which component data of thecorresponding service is transmitted in a broadcast stream. Asource_IP_addr field can indicate the source IP address of an IPdatagram including the component data of the corresponding service whenthe source_IP_address_flag is 1. A dest_IP_addr field can indicate thedestination IP address of the IP datagram including the component dataof the corresponding service. A dest_UDP_port field can indicate the UDPport number of the IP datagram including the component data of thecorresponding service. An LSID_DP field can indicate the identifier of adata pipe of a physical layer, which delivers signaling includingdetailed information about a transport session. In the case of ROUTE,for example, the signaling including the detailed information about thetransport session can be LCT session instance description includinginformation about an LCT transport session of a ROUTE session. Aservice_signaling_flag field can indicate whether service signaling istransmitted through the corresponding transport session. Theservice_signaling_flag field can indicate presence of a DP includingservice signaling when the value thereof is 1. A signaling_data_versionfield can indicate a change of related service signaling data. The valueof the signaling_data_version field can increase by 1 whenever theservice signaling data is changed. The receiver can detect a change ofsignaling related to the corresponding service using thesignaling_data_version field. A signaling_DP field can indicate theidentifier of a data pipe of the physical layer, which delivers servicesignaling. A transport session descriptors field can include transportsession level descriptors. Each descriptor can be extended and include anum_descriptors field. Each descriptor can include as many descriptorloops as a number corresponding to a value indicated by thenum_descriptors field. The transport session descriptors field caninclude transport session level descriptors. A service descriptors fieldcan include service level descriptors. A partition descriptors field caninclude a partition level descriptor, and one partition can indicatepart of broadcast streams used by a single broadcaster. An FIC sessiondescriptors field can include FIC level descriptors. According to anembodiment, the fields included in the FIC may be included in a tableother than the FIC and transmitted along with a broadcast signal.

FIG. 51 illustrates a method for transmitting FIC based signalingaccording to another embodiment of the present invention. Theaforementioned example of delivering FIC based signaling is as shown inthe figure. In the specification, FIC based signaling can be referred toas service acquisition information or service acquisition signaling. Asshown in the figure, physical layer signaling can include a field withrespect to the service acquisition information. The field with respectto the service acquisition information can indicate whether the serviceacquisition information FIC is parsed to the receiver. The receiver cancheck whether service signaling data has been changed throughservice_data_version information by parsing the service acquisitioninformation. When the service signaling data has been changed, thebroadcast signal receiver can acquire LSID or an LSID table, whichincludes detailed information about the corresponding transport session,using an LSID_DP field through a DP identified from the LSID_DP field.In addition, the receiver can recognize a change of signaling data usinginformation such as the service_signaling_flag, signaling_data_versionand signaling_DP and acquire the signaling data through an identifiedDP.

That is, the signaling method of the future broadcast system can includea sequence of confirming detailed information about the transportsession by signaling whether the service acquisition information isparsed through the physical layer signaling and signaling the positionof the detailed information about the transmission session through theservice acquisition information. Here, the detailed information aboutthe transport session can include an MPD transport table, an applicationsignaling table, a transport session descriptor (LSID) and/or acomponent mapping table (CMT), and detailed information of transmissionsessions can be delivered according to different examples.

FIG. 52 illustrates a service signaling message format of the futurebroadcast system according to an embodiment of the present invention. Inthe specification, a service signaling message can be referred to assignaling data or service layer signaling including detailed informationabout services. The service signaling message may include a signalingmessage header and a signaling message. The signaling message can berepresented in a binary or XML format. The signaling message can beincluded in an IP datagram or a payload of an application layertransport packet (e.g. ROUTE or MMTP packet) and transmitted. Thesignaling message header may have the following syntax and can berepresented in a format such as XML. The signaling message header caninclude the following fields. A signaling_id field can indicate asignaling message identifier. For example, when the signaling message isrepresented in the form of a section, the signaling_id field canindicate the ID of a signaling table section. A signaling_length fieldcan indicate the length of the signaling message. Asignaling_id_extension field can indicate extension information aboutthe identifier of the signaling message. The signaling_id_extensionfield can be used as signaling identification information along with thesignaling_id field. For example, the signaling_id_extension field caninclude the protocol version of the signaling message. A version_numberfield can indicate version information of the signaling message. Theversion_number field can be changed when the contents of the signalingmessage are changed. A current_next_indicator field can indicate whetherthe signaling message is currently available. The current_next_indicatorfield can indicate that the signaling message is currently availablewhen the value thereof is 1. The current_next_indicator field canindicate that the signaling message is not currently available and asignaling message including the same signaling_id,signaling_id_extension or fragment_number may be available in the futurewhen the value thereof is 0. A fragmentation_indicator field canindicate whether the signaling message has been fragmented. Thefragmentation_indicator field indicates that the corresponding signalingmessage has been fragmented when the value thereof is 1. In this case,inclusion of part of signaling data can be indicated throughsignaling_message_data( ). When the value of the fragmentation_indicatorfield is 0, inclusion of the entire signaling data can be indicatedthrough signaling_message_data( ). A payload_format_indicator field canindicate whether the current signaling message header includes apayload_format value. A payload_format_indicator field value of 1 canindicate that the signaling message header includes a payload_formatvalue. An expiration_indicator field can indicate whether the currentsignaling message header includes an expiration value. Anexpiration_indicator field value of 1 can indicate that the signalingmessage header includes an expiration value. A fragment_number field canindicate a fragment number of the current signaling message when asingle signaling message is divided into multiple fragments andtransmitted. A last_fragment_number field can indicate the number of afragment including the last data of the corresponding signaling messagewhen a single signaling message is divided into multiple fragments andtransmitted. A payload_format field can indicate the format of signalingmessage data included in a payload. In an embodiment, the payload_formatfield can be represented in a binary or XML format. An expiration fieldcan indicate effective time of the signaling message included in thepayload.

FIG. 53 shows service signaling tables used in the future broadcastsystem according to an embodiment of the present invention. Servicesignaling tables/messages according to the present invention are asdescribed below and can include the following information and besignaled. Information included in tables/messages can be individuallytransmitted per table and is not limited to the illustrated embodiments.According to an embodiment, signaling information belonging to differenttables may be merged into one table and transmitted. A service mappingtable can include service attributes and service related information.For example, attribute information of services can include informationsuch as IDs, names and categories of the services, and informationrelated to services can include information about paths through whichthe services can be acquired. An MPD delivery table can include DASH MPDrelated to services/content or information on paths through which DASHMPD can be acquired. A component mapping table can include componentinformation in services and component related information. The componentinformation can include related DASH representation information, and thecomponent related information can include information on paths throughwhich components can be acquired. An LSID table can include informationabout transport sessions for delivering services/components andtransport packet configurations. An initialization segment deliverytable can include initialization segment information about DASHrepresentation related to components in services or information aboutpaths through which the initialization segment information can beacquired. An application parameter table can include detailedinformation about applications relate to broadcast services andinformation about paths through which the detailed information can beobtained. When such signaling messages/tables are transmitted through abroadcast network, the signaling messages/tables can be transmittedthrough a fast information channel (FIC), a service signaling channel(SSC), an application layer transport session (e.g., ROUTE or MMTPsession) or the like. Furthermore, the signaling messages/tables can betransmitted over the Internet (broadband).

FIG. 54 shows a service mapping table used in the future broadcastsystem according to an embodiment of the present invention. Thefollowing description may be transmitted by being included in a servicesignaling message part following a signaling message header.

The service mapping table can include information about service mappingsignaling and can be represented in XML or binary format. The servicemapping table corresponding to service signaling information can includeservice identifier information, service type information, service nameinformation, channel number information, ROUTE session relatedinformation, MPD related information and component signaling positioninformation. The service identifier can indicate information identifyinga service and can be represented as an id attribute. The service typeinformation can indicate the type of the service and can be representedas a serviceType attribute. The service name information can indicatethe name of the service and can be represented as a serviceNameattribute. The channel number information can indicate a channel numberrelated to the service and can be represented as a channelNumberattribute.

The ROUTE session related information can include sourceIP,destinationIP and destinationPort attributes. The sourceIP attribute canindicate a source address of IP datagrams carrying associated data. ThedestinationIP attribute can indicate a destination address of the IPdatagrams carrying associated data. The destinationPort attribute canindicate a destination port number of the IP datagrams carryingassociated data.

In addition, the ROUTE session related information can include detailedinformation (LSID) about transport sessions. For example, the ROUTEsession related information can include LSID location information anddelivery mode information of LSID location information. Furthermore, thedetailed information LSID about transport sessions can include bootstrapinformation. The bootstrap information included in LSID can include LSIDbootstrap information according to delivery mode. Attributes included inthe bootstrap information will be described in detail below.

The MPD related information can include information about MPD or MPDsignaling location. The information about MPD can include a versionattribute and indicate the version of MPD. The MPD signaling locationinformation can indicate a location where signaling related to MPD orMPD URL can be acquired. Delivery mode information included in MPDsignaling location can indicate a delivery mode of the MPD locationsignaling. Bootstrap information included in the MPD signaling locationcan include bootstrap information of MPD or MPD URL according to thedelivery mode.

The component signaling location related information can include adelivery mode attribute. The delivery mode attribute can indicate adelivery mode of corresponding component signaling location information.The bootstrap information included in the MPD signaling location caninclude bootstrap information of corresponding component locationsignaling according to the delivery mode.

The bootstrap information can include at least one of the followingattributes according to delivery mode.

A sourceIP attribute can indicate a source address of IP datagramscarrying associated data. A destinationIP attribute can indicate adestination address of the IP datagrams carrying associated data. AdestinationPort attribute can indicate a destination port number of theIP datagrams carrying associated data. A tsi attribute can include theidentifier of a transport session delivering transport packets carryingassociated data. A URL attribute can indicate a URL where associateddata can be acquired. A packetid attribute can indicate the identifierof transport packets carrying associated data.

FIG. 55 shows a service signaling table of the future broadcast systemaccording to an embodiment of the present invention. The futurebroadcast system can provide broadcast service signaling such that thereceiver can receive broadcast services and content. This allows thereceiver to acquire related signaling when signaling data is transmittedthrough the same transport session identifier TSI. The service signalingtable can be represented in a binary format as illustrated and may berepresented in other formats such as XML according to embodiments. Inaddition, the service signaling table can encapsulated in theaforementioned signaling message format. The service signaling table caninclude the following fields. An SST_portocol_version field can indicatethe version of the service signaling table. A partition_id field canindicate the identifier of a corresponding partition. AnSST_data_version field can indicate the data version of thecorresponding service signaling table. A num_services field can indicatethe number of one or more services included in the correspondingpartition. A service_id field can indicate the identifier of thecorresponding service. A service_name field can indicate the name of thecorresponding service. An MPD_availability field can indicate whetherMPD can be acquired through broadcast, a cellular network and/orWi-Fi/Ethernet. A CMT_availability field can indicate whether acomponent mapping table (CMT) can be used through broadcast, a cellularnetwork and/or Wi-Fi/Ethernet. An ASL_availability field can indicatewhether an application signaling table (AST) can be used throughbroadcast, a cellular network and/or Wi-Fi/Ethernet. A DP_ID field canindicate the identifier of a DP carrying the MPD, CMT and/or ASL throughbroadcast. An LCT_IP_address field can indicate the IP address of an LCTchannel delivering the MPD, CMT and/or ASL. An LCT_UDP_port field canindicate a UDP port of the LCT channel delivering the MPD, CMT and/orASL. An LCT_TSI field can indicate a transport session identifier (TSI)of the LCT channel delivering the MPD, CMT and/or ASL. An MPD_TOI fieldcan indicate the transport object identifier of the MPD when the MPD isdelivered through broadcast. A CMT TOI field can indicate the transportobject identifier of the CMT when the CMT is delivered throughbroadcast. An AST_TOI field can indicate the transport object identifierof the AST when the AST is delivered through broadcast. An MPD_URL fieldcan indicate a URL where the MPD can be acquired through broadband. ACMT_URL field can indicate a URL where the CMT can be acquired throughbroadband. An AST_URL field can indicate a URL where the AST can beacquired through broadband.

FIG. 56 shows a component mapping table used in the future broadcastsystem according to an embodiment of the present invention. Thefollowing description may be transmitted by being included in a servicesignaling message part following a signaling message header. Thecomponent mapping table can include information about component mappingsignaling and can be represented in XML or binary format. The componentmapping table corresponding to service signaling information can includethe following fields. A Signaling_id field can include an identifierindicating that the corresponding table is the component mapping table.A protocol_version field can indicate a protocol version of thecomponent mapping table, such as a component mapping table syntax. ASignaling_version field can indicate a change of signaling data of thecomponent mapping table. A Service_id field can indicate the identifierof a service associated with corresponding components. A Num_componentfield can indicate the number of components included in thecorresponding service. An Mpd_id field can indicate a DASH MPDidentifier associated a component. A Period_id field can indicate a DASHperiod identifier associated with the component. A representation_idfield can indicate a DASH representation identifier associated with thecomponent. A Source_IP field can indicate a source IP address of IP/UDPdatagrams carrying corresponding component data. A Dest_IP field canindicate a destination IP address of the IP/UDP datagrams carrying thecorresponding component data. A port field can indicate a port number ofthe IP/UDP datagrams carrying the corresponding component data. A tsifield can indicate the identifier of an application layer transportsession carrying the corresponding component data. A DP_id field canindicate the identifier of a physical layer data pipe carrying thecorresponding component data. The CMT can define components associatedwith each service and signal, to the receiver, locations or paths wherethe corresponding components can be received through the aforementionedinformation.

FIG. 57 illustrates component mapping table description according to anembodiment of the present invention. Component mapping description cansignal information about transport paths of components included inbroadcast services in the future broadcast system. Component mappingtable description may be represented in XML format or as a binarybitstream. Component mapping table description can include the followingelements and attributes. A service_id attribute can indicate theidentifier of a service associated with a component. BroadcastComp canindicate one or more components transmitted through the same broadcaststream. BroadcastComp can include mpdID, perID, reptnID, baseURL and/ordatapipeID attributes. The mpdID attribute can indicate a DASH MPDidentifier associated with BroadcastComp. The perID attribute canindicate an associated period identifier in corresponding MPD. ThereptnID attribute can indicate a DASH representation identifierassociated with the corresponding component. The baseURL attribute canindicate a base URL of a DASH segment associated with the correspondingcomponent. The datapipeID attribute can indicate the identifier of adata pipe carrying corresponding component data in a broadcast stream.

BBComp can indicate one or more components transmitted through abroadband network. BBComp can include mpdID, perID, reptnID and/orbaseURL attributes. The mpdID attribute can indicate a DASH MPDidentifier associated with BBComp. The perID attribute can indicate anassociated period identifier in corresponding MPD. The reptnID attributecan indicate a DASH representation identifier associated with thecorresponding component. The baseURL attribute can indicate a base URLof a DASH segment associated with the corresponding component.

ForeignComp can indicate one or more components transmitted throughother broadcast streams. ForeignComp can include mpdID, perID, reptnID,baseURL, transportStreamID, sourceIPAddr, destIPAddr, destUDPPort and/ordatapipeID attributes. The mpdID attribute can indicate a DASH MPDidentifier associated with ForeignComp. The perID attribute can indicatean associated period identifier in corresponding MPD. The reptnIDattribute can indicate a DASH representation identifier associated withthe corresponding component. The baseURL attribute can indicate a baseURL of a DASH segment associated with the corresponding component. ThetransportStreamID attribute can indicate the identifier of a broadcaststream including corresponding component data. The sourceIPAddrattribute can indicate a source IP address of IP datagrams carrying thecorresponding component data. The destIPAddr attribute can indicate adestination IP address of the IP datagrams carrying the correspondingcomponent data. The destUDPPort attribute can indicate a destination UDPport number of the IP datagrams carrying the corresponding componentdata. The datapipeID attribute can indicate the identifier of a datapipe through which the corresponding component data is transmitted inthe corresponding broadcast stream. The aforementioned component mappingdescription can be transmitted by being encapsulated in an XML file orthe above-described signaling message format. As shown in the lower partof FIG. 57, a signaling message header can have the aforementionedformat and component mapping description or part thereof can be includedin the service message part. The CMT can define components associatedwith each service and signal, to the receiver, locations or paths wherethe corresponding components can be received through the aforementionedinformation.

FIG. 58 illustrates a syntax of the component mapping table of thefuture broadcast system according to an embodiment of the presentinvention. The future broadcast system can signal the component mappingtable such that the receiver can acquire components of broadcastservices. The component mapping table can be represented in binary, XMLor other formats and can be encapsulated in the aforementioned signalingmessage format. The component mapping table can include the followingfields. A CMT_portocol_version field can indicate the version of thestructure of the component mapping table (CMT). A service_id field canindicate the identifier of a service related to a component positionprovided by the corresponding CMT. A CMT_data_version field can indicatethe data version of the CMT. A num_broadcast_streams field can indicatethe number of broadcast streams including at least one component relatedto the corresponding service. A TSID field can indicate a transportsession identifier of a corresponding broadcast stream. A num_partitionsfield can indicate the number of partitions of a broadcast streamincluding at least one component related to the corresponding service.The CMT can include a plurality of partitions. A partition_id field canindicate the identifier of a corresponding partition. A num_data_pipesfield can indicate the number of data pipes in a partition including atleast one component related to the corresponding service. A DP_ID fieldcan indicate the identifier of each data pipe. A num_ROUTE_sessionsfield can indicate the number of transport sessions (e.g. ROUTEsessions) included in each data pipe. Each data pipe can include atleast one component associated with the corresponding service. AnIP_address field can indicate the IP address of each transport session.A UDP_port field can indicate a UDP port of each transport session. Anum_LCT_channels field can indicate the number of LCT channels in atransport session including a component associated with thecorresponding service. An LCT_TSI field can indicate a transport sessionidentifier (TSI). A Representation_ID field can indicate the identifierof representation carried by a corresponding LCT channel. AnInternet_availability field can be an identifier indicating whethercorresponding representation can be received through the Internet orbroadband. A num_internet_only_reptns field can indicate the number ofrepresentations which can be received only through the Internet orbroadband. A Representation_ID field can indicate the identifier ofrepresentation which can be received only through the Internet orbroadband in a loop of num_internet_only_reptns. The CMT can definecomponents associated with each service and signal, to the receiver,locations or paths where the corresponding components can be receivedthrough the aforementioned information.

FIG. 59 illustrates a method for delivering signaling related eachservice through a broadband network in the future broadcast systemaccording to an embodiment of the present invention. The futurebroadcast system can transmit signaling related to a service to thereceiver through a broadband network. The future broadcast system cantransmit signaling to the receiver through the broadband network usingURL signaling table description. The URL signaling table description canbe represented in XML or binary format. The URL signaling tabledescription can include the following attributes. A service_id attributecan indicate the identifier of a service associated with signaling. AnmpdURL attribute can indicate the URL of broadband MPD. A cstURLattribute can indicate the URL of a broadband CMT. The CMT can includeinformation about a path through which component data in a broadcastservice is acquired. An astURL attribute can indicate the URL of abroadband AST. The AST can include information about an applicationrelated to a broadcast service. The receiver can receive the descriptionand receive the corresponding signaling on the basis of the URL of eachsignaling. The aforementioned URL signaling table description can beencapsulated in a single XML file or the aforementioned signalingmessage format and transmitted. As shown in the lower part of thefigure, a signaling message header can take the aforementioned formatand the URL signaling table description or part thereof can follow thesignaling message header.

FIG. 60 illustrates a method for signaling MPD in the future broadcastsystem according to an embodiment of the present invention. As shown inthe upper part of the figure, a signaling message about MPD of abroadcast service available in a future broadcast network can becomposed of a signaling message header and the signaling message. Thesignaling message header can take the aforementioned format and MPDdelivery table information can include the following information.Signaling_id information can indicate that the corresponding signalingmessage is a signaling message including MPD or information about a paththrough which the MPD can be acquired. protocol_version information canindicate a protocol version of an MPD delivery table, such as the syntaxof the signaling message. Signaling_version information can indicate achange of signaling data of the MPD delivery table. Service_idinformation can indicate the identifier of a service associated with thecorresponding signaling information. Mpd_id information can indicate theidentifier of DASH MPD associated with the signaling message.MPD_version information is version information indicating a change ofthe corresponding MPD. Delivery_mode information can indicate whetherthe signaling message includes the corresponding MPD or is deliveredthrough a different path. MPD_data( ) information can include MPD datawhen the signaling message includes the MPD. MPD_path information caninclude information about a path through which the MPD can be acquired.For example, the path can indicate a URL.

MPD delivery table description can include the following information. Aservice_id attribute can indicate the identifier of a service associatedwith signaling. An MPD id attribute can indicate the identifier of theMPD. MPD_version is version information indicating a change of the MPD.An MPD_URL attribute can include information about a URL through whichthe MPD can be acquired. An MPD element can include MPD information. TheMPD delivery table description can be encapsulated in a single XML fileor the aforementioned signaling message format and transmitted. That is,the signaling message header can take the aforementioned format and theMPD delivery table description or part thereof can follow the signalingmessage header.

FIG. 61 illustrates a syntax of an MPD delivery table of the futurebroadcast system according to an embodiment of the present invention.Information of the MPD delivery table or part thereof can follow asignaling message header. The information of the MPD delivery table caninclude the following fields. A service_id field can indicate theidentifier of an associated broadcast service. An MPD_id_length fieldcan indicate the length of the following MPD_id_bytes( ). AnMPD_id_bytes field can indicate the identifier of an MPD filed includedin a signaling message. An MPD_version field can indicate versioninformation such as a change of data of the corresponding MPD. AnMPD_URL_availability field can indicate presence or absence of URLinformation of the MPD in the corresponding signaling table/message. AnMPD_data_availability field can indicate whether the correspondingsignaling table/message includes the MPD. The MPD_data_availabilityfield can indicate that the signaling table/message includes the MPDwhen the value thereof is 1. An MPD_URL_length field can indicate thelength of the following MPD_URL_bytes( ). An MPD_URL_bytes field canindicate an MPD URL included in the signaling message. An MPD_codingfield can indicate an encoding scheme of an MPD field included in thesignaling message. As shown in the lower part of the figure, an MPD filecan be encoded according to different encoding schemes according tovalues of the MPD_coding field. For example, an MPD_coding field valueof “0x00” can indicate that the signaling table/message includes a plainMPD field represented in XML. An MPD_coding field value of “0x01” canindicate that the signaling table/message includes an MPD fieldcompressed by gzip. If an MPD field compressed by gzip is segmented andrespectively transmitted through a plurality of messages/tables,corresponding multiple MPD_bytes( ) can be concatenated and thenungzipped. An MPD_byte_length field can indicate the length of thefollowing MPD_bytes( ). An MPD_bytes field can include data of the MPDfield included in the signaling message according to the encoding schemeindicated by the MPD_coding field. The future broadcast system enablesthe receiver to receive or acquire service related MPD through the MPDdelivery table including the aforementioned fields.

FIG. 62 illustrates transport session instance description of the futurebroadcast system according to an embodiment of the present invention.When an application layer transmission method corresponds to real-timeobject delivery over unidirectional transport (ROUTE), a ROUTE sessioncan be composed of one or more layered coding transport (LCT) sessions.Detailed information about one or more transport sessions can besignaled through transport session instance description. In the case ofROUTE, the transport session instance description may be referred to asLCT session instance description (LSID). Particularly, the transportsession instance description can define what is delivered through eachLCT transport session constituting the ROUTE session. Each transportsession can be uniquely identified by a transport session identifier(TSI). The TSI can be included in an LCT header. The transport sessioninstance description can describe all transport sessions carried by thecorresponding session. For example, LSID can describe all LCT sessionscarried by a ROUTE. The transport session instance description may bedelivered through the same ROUTE session as transport sessions orthrough a different ROUTE session or unicast.

When delivered through the same ROUTE session, the transport sessioninstance description can be delivered through a transport session havinga TSI of 0. While an object referred to in the transport sessioninstance description may be delivered through the transport session withTSI=0, the object can have a TOI value different from that of thetransport session instance description. Otherwise, the object may bedelivered through a separate transport session with TSI≠0. The transportsession instance description can be updated using at least one of theversion number, validity information and expiration information. Thetransport session instance description can be represented in a bitstreamin addition to the illustrated format.

The transport session instance description can include version,validFrom and expiration attributes and include a TSI attribute andSourceFlow and RepairFlow information with respect to each transportsession. The version attribute can indicate the version information ofthe transport session instance description, and the version informationcan increase whenever contents thereof are updated. Transport sessioninstance description having a highest version number is the currentlyvalid version. The validFrom attribute can indicate the data and timefrom which the corresponding transport session instance description isvalid. The validFrom attribute may not be included in the transportsession instance description according to embodiment. In this case, thereceiver can assume that the corresponding transport session instancedescription is valid immediately. The expiration attribute can indicatethe date and time when the corresponding transport session instancedescription expires. The expiration attribute may not be included in thetransport session instance description. In this case, the receiver canassume that the corresponding transport session instance description isvalid for all time. If transport session instance description having anexpiration attribute is received, the transport session instancedescription can conform to the corresponding expiration attribute. TheTSI attribute can indicate a transport session identifier. A SourceFlowelement provides information of a source flow transmitted with thecorresponding TSI. The SourceFlow element will be described in detailbelow. A RepairFlow element can provide information of a repair flowtransmitted with the corresponding TSI.

FIG. 63 illustrates shows a SourceFlow element of the future broadcastsystem according to an embodiment of the present invention. TheSourceflow element can include an EFDT element, an idRef attribute, arealtime attribute, a minBufferSize attribute, an Application Identifierelement and a PayloadFormat element. The EFDT element can specifydetailed information of file delivery data. The EFDT element indicatesan extended file delivery table (FDT) instance and will be described indetail below. The idRef attribute can indicate an EFDT identifier andcan be represented as a URI by the corresponding transport session. Therealtime attribute can indicate that corresponding LCT packets includeextension headers. The extended headers can include timestampsindicating presentation time of an included delivery object. TheminBufferSize attribute can define the maximum amount of data that needsto be stored in the receiver. The Application Identifier element canprovide additional information that can be mapped to the applicationcarried in the corresponding transport session. For example,representation ID of DASH content or Application Set parameters of aDASH representation can be provided as additional information in orderto select a transport session for rendering. The PayloadFormat elementcan define payload formats of ROUTE packets carrying objects of thesource flow. The PayloadFormat element can include a codePointattribute, a deliveryObjectFormat attribute, a fragmentation attribute,a deliveryOrder attribute, a sourceFecPayloadID attribute and/or anFECParameters element. The codePoint attribute can define a code pointused in the corresponding payload. This can indicate the value of the CPfield in the LCT header. The deliveryObjectFormat attribute can indicatethe payload format of the corresponding delivery object. Thefragmentation attribute can define the type of fragmentation. ThedeliveryOrder attribute can indicate the order of delivery of objects.The sourceFecPayloadID attribute can define the format of a source FECpayload identifier. The FECParameters element can define FEC parameters.This includes an FEC encoding id, an instance id, etc.

FIG. 64 shows an EFDT of the future broadcast system according to anembodiment of the present invention. The EFDT can include detailedinformation of file delivery data. The EFDT can include an idRefattribute, a version attribute, a maxExpiresDelta attribute, amaxTransportSize attribute and a FileTemplate element. The idRefattribute can indicate the identifier of the EFDT. The version attributecan indicate the version of an EFDT instance descriptor. This attributecan be increased by 1 when the EFDT is updated. A received EFDT with thehighest version number can be the currently valid version. ThemaxExpiresDelta attribute can indicate a maximum expiry time for anobject after sending a first packet associated to the object. ThemaxTransportSize attribute can indicate a maximum transport size of anobject described by the corresponding EFDT. The FileTemplate element canspecify the file URL or file template in the body.

The aforementioned transport session instance descriptor (LSID) elementcan be transmitted according to a transport session instance descriptor(LSID) table shown in the lower part of the figure. The LSID table canbe delivered through the aforementioned signaling message which isdivided into a signaling message header and a signaling message datapart. The signaling message data part can include the transport sessioninstance descriptor (LSID) or part thereof. Signaling message data caninclude the LSID table and the following fields. A Signaling_id field isidentifier information indicating that the corresponding table is asignaling table including the LSID. A protocol_version field canindicate the protocol version of signaling, such as a signaling syntaxincluding the LSID. A Signaling_version field can indicate a change ofsignaling data including the LSID. In addition, the LSID table mayfurther include the contents of the aforementioned transport sessioninstance descriptor (LSID) element.

FIG. 65 illustrates a method for transmitting an initialization segmentdelivery table (ISDT) used in the future broadcast system according toan embodiment of the present invention. The future broadcast system candeliver signaling information about an initialization segment of DASHrepresentation associated with a component in a broadcast service bytransmitting an ISDT. The signaling information about the initializationsegment of DASH representation associated with the component in thebroadcast service may include a header and data. The signaling messageheader can have the aforementioned format and the signaling message datacan include initialization segment delivery information or part thereof.The initialization segment delivery information can include thefollowing information. Signaling_id information can identify a signalingmessage including the initialization segment or information on the paththereof. protocol_version information can indicate the protocol versionof the ISDT, such as the syntax of the corresponding signaling message.Sequence_number information can indicate the instance identifier of theISDT. Signaling_version information can indicate a change of signalingdata of the ISDT. Service_id information can identify a serviceassociated with the corresponding component. Mpd_id information canindicate a DASH MPD identifier associated with the correspondingcomponent. period_id information can indicate a DASH Period identifierassociated with the corresponding component. representation_idinformation can indicate a DASH representation identifier associatedwith the corresponding component. Initialization_segment_versioninformation can be version information indicating a change of thecorresponding MPD. Delivery_mode information can indicate whether theISDT includes the initialization segment or is delivered through adifferent path. Initialization_segment_data( ) information can includethe initialization segment data itself. Initialization segment pathinformation can include information about a path through which theinitialization segment can be acquired, such as the URL of theinitialization segment. The receiver can receive information about theinitialization segment of DASH representation associated with thecorresponding component through the ISDT.

FIG. 66 illustrates a delivery structure of a signaling message of thefuture broadcast system according to an embodiment of the presentinvention. The aforementioned signaling data can be delivered asillustrated when transmitted based on application layer transport, forexample, ROUTE. That is, some signaling can be transmitted through afast information channel in order to support fast service scan. Somesignaling can be transmitted through a specific transport session anddelivered along with component data.

Signaling information for supporting fast service scan and acquisitioncan be received through a separate channel from a transport session.Here, the separate channel can refer to a separate data pipe (DP).Detailed information about a service can be received through a separatedesignated transport session. Here, the transport session can have avalue of TSI=0. Information delivered through the designated transportsession can include an MPD delivery table, an application signalingtable, a transport session instance description table and/or a componentmapping table. Some signaling information can be delivered through atransport session along with component data. For example, theinitialization segment delivery table can be delivered along withcomponent data.

The lower part of the figure illustrates an example of acquiringbroadcast services in the future broadcast network. When a service isselected, the receiver can tune to broadcast, acquire information forfast service scan and acquisition and parse the information. Upondetermination of the location of service layer signaling or transportsession instance description (TSID or LSID) from the information forfast service scan and acquisition, the receiver can acquire and parsethe corresponding description. In addition, the receiver can check thetransport session including the signaling, acquire a signaling tablefrom the transport session, parse the signaling table and determine adesired component. Through this process, the receiver can present thedesired component. That is, broadcast services can be provided to a userby acquiring information about a transport session from information forfast service scan and acquisition, confirming the location of a desiredcomponent from the information about the transport session andreproducing the component.

FIG. 67 shows signaling data transmitted, by the future broadcast systemaccording to an embodiment of the present invention, for fast broadcastservice scan. FIC information (service acquisition information) forsupporting fast broadcast service scan and service/component acquisitioncan include information about an application layer transport sessiondelivering service and component data. As illustrated, the FICinformation can be represented in a binary format. However, the FICinformation may be represented in other formats such as XML according toembodiments. The FIC information can include the following fields. AnFIC_portocol_version field can indicate the version of the structure ofsignaling information. A TSID field can indicate the identifier of abroadcast stream. An FIC_data_version field can indicate the dataversion of the corresponding FIC information. An FIC_data_version fieldcan be increased when the contents of the FIC are changed. Anum_partitions field can indicate the number of partitions of abroadcast stream. It is assumed that each broadcast stream can bedivided into one or more partitions and transmitted in order to use thenum_partitions field. Each partition can include a plurality of DPs by asingle broadcaster. Each partition can indicate a part of a broadcaststeam, used by a single broadcaster. A partition_id field can indicatethe identifier of the corresponding partition. Apartition_protocol_version field can indicate the version of theaforementioned partition structure. A num_services field can indicatethe number of one or more components included in the correspondingpartition. A service_id field can indicate a service identifier. Aservice_data_version field can indicate a change of service loop data inthe FIC or a change of service signaling data associated with thecorresponding service. A service_data_version field can be increased by1 whenever included service data is changed. The receiver can detect aservice loop data change of the FIC or a change of signaling associatedwith the corresponding service using the service_data_version field. Achannel_number field can indicate the channel number associated with thecorresponding service. A service_category field can indicate thecategory of the corresponding service. For example, the service_categoryfield can indicate A/V, audio, ESG, CoD, etc. Ashort_service_name_length field can indicate the length of the name ofthe corresponding service. A short_service_name field can indicate thename of the corresponding service. A service_status field can indicatethe status of the corresponding service and represent an active orsuspended attribute and a hidden or shown attribute according to thevalue thereof. A service_distribution field can have an attributesimilar to “multi-ensemble” flag of ATSC M/H. For example, theservice_distribution field can indicate information about whether thecorresponding service is included in the corresponding partition, theservice is presentable only with the corresponding partition althoughthe service is partially included in the partition, another partition isnecessary for presentation, or other broadcast streams are necessary forpresentation. An sp_indicator field is a service protection flag and canindicate whether one or more components necessary for presentation areprotected. An IP_version_flag field can indicate the following IPaddress format. The IP_version_flag field can indicate that IPv4 is usedwhen the value thereof is 0 and indicate that IPv6 is used when thevalue thereof is 1. A source_IP_address_flag field can indicate whetherthe FIC information includes source_IP_addr. The source_IP_address_flagfield can indicate presence of source_IP_addr when the value thereofis 1. A num_transport_session field can indicate the number of transportsessions (e.g. ROUTE or MMTP sessions) in which component data of thecorresponding service is transmitted in a broadcast stream. Asource_IP_addr field can indicate the source IP address of an IPdatagram including the component data of the corresponding service whenthe source_IP_address_flag is 1. A dest_IP_addr field can indicate thedestination IP address of the IP datagram including the component dataof the corresponding service. A dest_UDP_port field can indicate the UDPport number of the IP datagram including the component data of thecorresponding service. An LSID_DP field can indicate the identifier of adata pipe of a physical layer, which delivers signaling includingdetailed information about a transport session. In the case of ROUTE,for example, the signaling including the detailed information about thetransport session can be LCT session instance description includinginformation about an LCT transport session of a ROUTE session. AnLSID_tsi field can indicate the identifier of a transport sessionthrough which transport session instance description that is signalingincluding detailed information about transport sessions is transmitted.Here, the transport session instance description can be LSID in the caseof an LCT transmission session. In addition, signaling associated withthe corresponding service can be delivered through the transport sessionin which the transport session instance description is transmitted. Aservice_signaling_flag field can indicate whether service signaling istransmitted through the corresponding transport session. Theservice_signaling_flag field can indicate presence of a DP includingservice signaling when the value thereof is 1. A signaling_data_versionfield can indicate a change of related service signaling data. The valueof the signaling_data_version field can increase by 1 whenever theservice signaling data is changed. The receiver can detect a change ofsignaling related to the corresponding service using thesignaling_data_version field. A signaling_DP field can indicate theidentifier of a data pipe of the physical layer, which delivers servicesignaling. A signaling_tsi field can indicate the identifier of atransport session delivering service signaling. A transport sessiondescriptors field can include transport session level descriptors. Eachdescriptor can be extended and include a num_descriptors field. Eachdescriptor can include as many descriptor loops as the number indicatedby the num_descriptors field. The transport session descriptors fieldcan include transport session level descriptors. A service descriptorsfield can include service level descriptors. A partition descriptorsfield can include a partition level descriptor, and one partition canindicate part of broadcast streams used by a single broadcaster. An FICsession descriptors field can include FIC level descriptors. Accordingto an embodiment, the fields included in the FIC may be included in atable other than the FIC and transmitted along with a broadcast signal.

FIG. 68 shows signaling data transmitted, by the future broadcast systemaccording to an embodiment of the present invention, for fast broadcastservice scan. FIC information (service acquisition information) forsupporting fast broadcast service scan and service/component acquisitioncan include information about an application layer transport sessiondelivering service and component data. As illustrated, the FICinformation can be represented in a binary format. However, the FICinformation may be represented in other formats such as XML according toembodiments. The FIC information can include the following fields. AnFIC_portocol_version field can indicate the version of the structure ofsignaling information. A num_partitions field can indicate the number ofpartitions of a broadcast stream. It is assumed that each broadcaststream can be divided into one or more partitions and transmitted inorder to use the num_partitions field. Each partition can include aplurality of DPs by a single broadcaster. Each partition can indicate apart of a broadcast steam, used by a single broadcaster. A partition_idfield can indicate the identifier of the corresponding partition. Apartition_protocol_version field can indicate the version of theaforementioned partition structure. A num_services field can indicatethe number of one or more services included in the correspondingpartition. Each service can include a plurality of signaling tables. Forexample, each service can include DASH MPD containing components andinformation about segments thereof, a CMT containing identifiers ofcomponents included in broadband and other broadcast streams, anapplication signaling table (AST) and a URL signaling table (UST)including at least one of the URLs of the MPD, CMT and AST. Thesesignaling tables can be included in a signaling channel of thecorresponding service. A service_id field can indicate a serviceidentifier. A service_data_version field can indicate a change ofservice loop data in the FIC or a change of service signaling dataassociated with the corresponding service. A service_data_version fieldcan be increased by 1 whenever included service data is changed. Forexample, a service_data_version field can be increased by 1 when theFIC, MPD, CMT, AST or UST is changed. The receiver can detect a serviceloop data change of the FIC or a change of signaling associated with thecorresponding service using the service_data_version field. Aservice_channel_number field can indicate the channel number associatedwith the corresponding service. A service_category field can indicatethe category of the corresponding service. For example, theservice_category field can indicate A/V, audio, ESG, CoD, etc. Ashort_service_name_length field can indicate the length of the name ofthe corresponding service. A short_service_name field can indicate thename of the corresponding service. A service_status field can indicatethe status of the corresponding service and represent an active orsuspended attribute and a hidden or shown attribute according to thevalue thereof. A service_distribution field can have an attributesimilar to the “multi-ensemble” flag of ATSC M/H. For example, theservice_distribution field can indicate information about whether thecorresponding service is included in the corresponding partition, theservice is presentable only with the corresponding partition althoughthe service is partially included in the partition, another partition isnecessary for presentation, or other broadcast streams are necessary forpresentation. An sp_indicator field is a service protection flag and canindicate whether one or more components necessary for presentation areprotected. An IP_version_flag field can indicate the following IPaddress format. The IP_version_flag field can indicate that IPv4 is usedwhen the value thereof is 0 and indicate that IPv6 is used when thevalue thereof is 1. A num_ROUTE_sessions field can indicate the numberof transport sessions delivering component data of the correspondingservice in a broadcast stream. For example, transport session can beROUTE sessions. The following information can be set per ROUTE session.A source_IP_addr field can indicate the source IP address of an IPdatagram including the component data of the corresponding service. Adest_IP_addr field can indicate the destination IP address of the IPdatagram including the component data of the corresponding service. Adest_UDP_port field can indicate the UDP port number of the IP datagramincluding the component data of the corresponding service. An LSID_DPfield can indicate the identifier of a data pipe of a physical layer,which delivers signaling including detailed information about atransport session. In the case of ROUTE, for example, the signalingincluding the detailed information about the transport session can beLCT session instance description including information about an LCTtransport session of a ROUTE session. An LSID_tsi field can indicate theidentifier of a transport session through which transport sessioninstance description that is signaling including detailed informationabout transport sessions is transmitted. Here, the transport sessioninstance description can be LSID in the case of an LCT transmissionsession. In addition, signaling associated with the correspondingservice can be delivered through the transport session in which thetransport session instance description is transmitted. Acomponent_signaling_flag field can indicate whether service signaling ofthe corresponding service is transmitted through the correspondingtransport session. When the component_signaling_flag is 1, this canindicate that data transmitted through the corresponding transportsession includes service signaling (e.g. MPD (DASH Media PresentationDescription), CMT or the like). Here, the CMT is a component mappingtable and can include identifiers of components delivered throughbroadband and also include information about components included inother broadcast streams. Each service can include service signalingchannels. The service signaling channels can include an MPD, a CMT, anAST and/or a UST. A service signaling channel may be a signaling channelfrom among a plurality of route sessions for services, and presence orabsence thereof can be indicated through the component signaling flag.When signaling and service components are transmitted through aplurality of transport sessions (ROUTE or MMTP sessions), theaforementioned service signaling tables can be preferably delivered by asingle transport session.

A ROUTE session descriptors field can include transport session leveldescriptors. Each descriptor can be extended and include anum_descriptors field. Each descriptor can include as many descriptorloops as the number indicated by the num_descriptors field. A transportsession descriptors field can include transport session leveldescriptors. A service descriptors field can include service leveldescriptors. A partition descriptors field can include a partition leveldescriptor, and one partition can indicate part of broadcast streamsused by a single broadcaster. An FIC session descriptors field caninclude FIC level descriptors.

According to an embodiment, the fields included in the FIC may beincluded in a table other than the FIC and transmitted along with abroadcast signal.

FIG. 69 illustrates component mapping table description according to anembodiment of the present invention. Component mapping description cansignal information about transport paths of components included inbroadcast services in the future broadcast system. Component mappingtable description may be represented in XML format or a binarybitstream. Component mapping table description can include the followingelements and attributes. A service_id attribute can indicate theidentifier of a service associated with a component. BroadcastComp canindicate one or more components transmitted through the same broadcaststream. BroadcastComp can include mpdID, perID, reptnID, baseURL and/ordatapipeID attributes. The mpdID attribute can indicate a DASH MPDidentifier associated with BroadcastComp. The perID attribute canindicate an associated period identifier in corresponding MPD. ThereptnID attribute can indicate a DASH representation identifierassociated with the corresponding component. The baseURL attribute canindicate a base URL of segments constituting DASH representationassociated with the corresponding component. The datapipeID attributecan indicate the identifier of a data pipe carrying correspondingcomponent data in a broadcast stream.

BBComp can indicate one or more components transmitted through abroadband network. BBComp can include mpdID, perID, reptnID and/orbaseURL attributes. The mpdID attribute can indicate a DASH MPDidentifier associated with BBComp. The perID attribute can indicate anassociated period identifier in corresponding MPD. The reptnID attributecan indicate a DASH representation identifier associated with thecorresponding component. The baseURL attribute can indicate a base URLof segments constituting DASH representation associated with thecorresponding component.

ForeignComp can indicate one or more components transmitted throughother broadcast streams. ForeignComp can include mpdID, perID, reptnID,baseURL, transportStreamID, sourceIPAddr, destIPAddr, destUDPPort and/ordatapipeID attributes. The mpdID attribute can indicate a DASH MPDidentifier associated with ForeignComp. The perID attribute can indicatean associated period identifier in corresponding MPD. The reptnIDattribute can indicate a DASH representation identifier associated withthe corresponding component. The baseURL attribute can indicate a baseURL of segments constituting DASH representation associated with thecorresponding component. The transportStreamID attribute can indicatethe identifier of a broadcast stream including corresponding componentdata. The sourceIPAddr attribute can indicate a source IP address of IPdatagrams carrying the corresponding component data. The destIPAddrattribute can indicate a destination IP address of the IP datagramscarrying the corresponding component data. The destUDPPort attribute canindicate a destination UDP port number of the IP datagrams carrying thecorresponding component data. The datapipeID attribute can indicate theidentifier of a data pipe through which the corresponding component datais transmitted in the corresponding broadcast stream. The sourceIPAddr,destIPAddr, destUDPPort and datapipeID attributes can be optionalaccording to embodiments and selectively included in the CMT. Theaforementioned component mapping description can be transmitted by beingencapsulated in an XML file or the above-described signaling messageformat. As shown in the lower part of the figure, a signaling messageheader can have the aforementioned format and component mappingdescription or part thereof can be included in the service message part.The CMT can define components associated with each service and signal,to the receiver, locations or paths where the corresponding componentscan be received through the aforementioned information.

FIG. 70 illustrates component mapping table description according to anembodiment of the present invention. Component mapping description cansignal information about transport paths of components included inbroadcast services in the future broadcast system. Component mappingtable description may be represented in XML format or a binarybitstream. Component mapping table description can include the followingelements and attributes. A service_id attribute can indicate theidentifier of a service associated with a component. BroadcastComp canindicate one or more components transmitted through the same broadcaststream. BroadcastComp can include mpdID, perID, reptnID, baseURL, tsiand/or datapipeID attributes. The mpdID attribute can indicate a DASHMPD identifier associated with BroadcastComp. The perID attribute canindicate an associated period identifier in corresponding MPD. ThereptnID attribute can indicate a DASH representation identifierassociated with the corresponding component. The baseURL attribute canindicate a base URL of segments constituting DASH representationassociated with the corresponding component. The tsi attribute canindicate the identifier of a transport session through whichcorresponding component data is transmitted in a broadcast stream. ThedatapipeID attribute can indicate the identifier of a data pipe carryingthe corresponding component data in the broadcast stream.

BBComp can indicate one or more components transmitted through abroadband network. BBComp can include mpdID, perID, reptnID and/orbaseURL attributes. The mpdID attribute can indicate a DASH MPDidentifier associated with BBComp. The perID attribute can indicate anassociated period identifier in corresponding MPD. The reptnID attributecan indicate a DASH representation identifier associated with thecorresponding component. The baseURL attribute can indicate a base URLof segments constituting DASH representation associated with thecorresponding component.

ForeignComp can indicate one or more components transmitted throughother broadcast streams. ForeignComp can include mpdID, perID, reptnID,baseURL, transportStreamID, sourceIPAddr, destIPAddr, destUDPPort, tsiand/or datapipeID attributes. The mpdID attribute can indicate a DASHMPD identifier associated with ForeignComp. The perID attribute canindicate an associated period identifier in corresponding MPD. ThereptnID attribute can indicate a DASH representation identifierassociated with the corresponding component. The baseURL attribute canindicate a base URL of segments constituting DASH representationassociated with the corresponding component. The transportStreamIDattribute can indicate the identifier of a broadcast stream includingcorresponding component data. The sourceIPAddr attribute can indicate asource IP address of IP datagrams carrying the corresponding componentdata. The destIPAddr attribute can indicate a destination IP address ofthe IP datagrams carrying the corresponding component data. ThedestUDPPort attribute can indicate a destination UDP port number of theIP datagrams carrying the corresponding component data. The tsiattribute can indicate the identifier of a transport session throughwhich the corresponding component data is transmitted in thecorresponding broadcast stream. The datapipeID attribute can indicatethe identifier of a data pipe through which the corresponding componentdata is transmitted in the corresponding broadcast stream. ThesourceIPAddr, destIPAddr, destUDPPort and datapipeID attributes can beoptional according to embodiments and selectively included in the CMT.The aforementioned component mapping description can be transmitted bybeing encapsulated in an XML file or the above-described signalingmessage format. As shown in the lower part of the figure, a signalingmessage header can have the aforementioned format and component mappingdescription or part thereof can be included in the service message part.The CMT can define components associated with each service and signal,to the receiver, locations or paths where the corresponding componentscan be received through the aforementioned information.

FIGS. 71 and 72 illustrate component mapping table description accordingto an embodiment of the present invention. Component mapping descriptioncan signal information about transport paths of components included inbroadcast services in the future broadcast system. Component mappingtable description may be represented in XML format or as a binarybitstream. Component mapping table description can include a deliveryparameter element and a payload format element along with the DASHassociated identifiers.

Component mapping table description can include the following elementsand attributes. A service_id attribute can indicate the identifier of aservice associated with a component. A component element can indicatecomponents in the corresponding broadcast service. The component elementcan include an mpdID attribute, a perID attribute, a reptnID attribute,a baseURL attribute, the delivery parameter element and/or the payloadformat element. The mpdID attribute can indicate a DASH MPD identifierassociated with a component. The perID attribute can indicate anassociated period identifier in corresponding MPD. The reptnID attributecan indicate a DASH representation identifier associated with thecorresponding component. The baseURL attribute can indicate a base URLof segments constituting DASH representation associated with thecorresponding component.

The delivery parameter element can include detailed information about apath through which the corresponding component is transmitted. Thedelivery parameter element can include transportStreamID, sourceIPAddr,destIPAddr, destUDPPort, tsi, datapipeID and/or URL attributes. ThetransportStreamID attribute can indicate the identifier of a broadcaststream including corresponding component data. The sourceIPAddrattribute can indicate a source IP address of IP datagrams carrying thecorresponding component data. The destIPAddr attribute can indicate adestination IP address of the IP datagrams carrying the correspondingcomponent data. The destUDPPort attribute can indicate a destination UDPport number of the IP datagrams carrying the corresponding componentdata. The tsi attribute can indicate the identifier of a transportsession through which the corresponding component data is transmitted inthe corresponding broadcast stream. The datapipeID attribute canindicate the identifier of a physical layer data pipe through which thecorresponding component data is transmitted in the correspondingbroadcast stream. The URL attribute can indicate URL information bywhich the corresponding component data can be acquired through theInternet. The sourceIPAddr, destIPAddr, destUDPPort, datapipeID and/orURL attributes can be optional according to embodiments and selectivelyincluded in the delivery parameter element.

The payload format element can include a codePoint attribute, adeliveryObjectFormat attribute, a fragmentation attribute, adeliveryOrder attribute, a sourceFecPayloadID attribute and/or anFECParameters element. The codePoint attribute can define a code pointused in the corresponding payload. This can indicate the value of the CPfield of the LCT header. The deliveryObjectFormat attribute can indicatethe payload format of the corresponding delivery object. Thefragmentation attribute can define the type of fragmentation. ThedeliveryOrder attribute can indicate the order of delivery of objects.The sourceFecPayloadID attribute can define the format of a source FECpayload identifier. The FECParameters element can define FEC parametersand include an FEC encoding id, an instance id, etc.

FIG. 73 illustrates component mapping table description according to anembodiment of the present invention. Component mapping description cansignal information about transport paths of components included inbroadcast services in the future broadcast system. Component mappingtable description may be represented in XML format or as a binarybitstream. Component mapping table can include a service_id attribute,an mpd_id attribute, a per_id attribute, a BroadcastComp element, aBBComp element and a ForeignComp element. Component mapping tabledescription can include the following elements and attributes. Theservice_id attribute can indicate the identifier of a service associatedwith a component. The CMT description can include mpdID and perIDattributes at the same level as the service_id attribute. That is, thempdID and perID attributes commonly applied to the BroadcastComp, BBCompand ForeignComp elements can be described at the same level as theservice_id attribute instead of being redundantly described. The mpdIDattribute can indicate a DASH MPD identifier associated with thecorresponding service. The perID attribute can indicate an associatedperiod identifier in corresponding MPD.

BroadcastComp can indicate one or more components transmitted throughthe same broadcast stream. BroadcastComp can include reptnID, baseURL,tsi and/or datapipeID attributes. The reptnID attribute can indicate aDASH representation identifier associated with the correspondingcomponent. The baseURL attribute can indicate a base URL of segmentsconstituting DASH representation associated with the correspondingcomponent. The tsi attribute can indicate the identifier of a transportsession through which the corresponding component data is transmitted inthe corresponding broadcast stream. The datapipeID attribute canindicate the identifier of a data pipe through which the correspondingcomponent data is transmitted in the corresponding broadcast stream.

BBComp can indicate one or more components transmitted through abroadband network. BBComp can include reptnID and/or baseURL attributes.The reptnID attribute can indicate a DASH representation identifierassociated with the corresponding component. The baseURL attribute canindicate a base URL of segments constituting DASH representationassociated with the corresponding component.

ForeignComp can indicate one or more components transmitted throughother broadcast streams. ForeignComp can include reptnID, baseURL,transportStreamID, sourceIPAddr, destIPAddr, destUDPPort, tsi and/ordatapipeID attributes. The reptnID attribute can indicate a DASHrepresentation identifier associated with the corresponding component.The baseURL attribute can indicate a base URL of segments constitutingDASH representation associated with the corresponding component. ThetransportStreamID attribute can indicate the identifier of a broadcaststream including corresponding component data. The sourceIPAddrattribute can indicate a source IP address of IP datagrams carrying thecorresponding component data. The destIPAddr attribute can indicate adestination IP address of the IP datagrams carrying the correspondingcomponent data. The destUDPPort attribute can indicate a destination UDPport number of the IP datagrams carrying the corresponding componentdata. The tsi attribute can indicate the identifier of a transportsession through which the corresponding component data is transmitted inthe corresponding broadcast stream. The datapipeID attribute canindicate the identifier of a data pipe through which the correspondingcomponent data is transmitted in the corresponding broadcast stream. ThesourceIP Addr, destIPAddr, destUDPPort and datapipeID attributes can beoptional according to embodiments and selectively included in the CMT.The aforementioned component mapping description can be transmitted bybeing encapsulated in an XML file or the above-described signalingmessage format. The CMT can define components associated with eachservice and inform the receiver of locations or paths where thecorresponding components can be received through the aforementionedinformation.

FIG. 74 shows common attributes and elements of MPD according to anembodiment of the present invention. The future broadcast system mayprovide DASH based hybrid broadcast services. In the future broadcastsystem, segments associated with representation in DASH MPD aredelivered through different distribution paths. The common attributesand elements of the MPD can be commonly present in adaptation set,representation and sub-representation elements and include locationinformation of associated representation as illustrated. The futurebroadcast system can enable a DASH client to recognize the associatedrepresentation or locations of segments using the location informationof the associated representation, included in the common attributes andelements of the MPD. The common attributes and elements of the MPD caninclude the following attributes and elements. @profiles attribute canindicate profiles of the associated representation. @width attribute canindicate the horizontal visual presentation size of a video media typeto be represented. @height attribute can indicate the vertical visualpresentation size of the video media type to be represented. @sarattribute can indicate the sample aspect ratio of video media componenttype. @frameRate attribute can indicate the output frame rate of thevideo media type in the representation. @audioSamplingRate attribute canindicate the sampling rate of an audio media component type. @mimeTypeattribute can indicate the MIME type of concatenation of theinitialization segment. @segmentProfiles attribute can indicate profilesof segments that are essential to process the representation. @codecsattribute can indicate the codec used in the representation.@maximumSAPPeriod attribute can indicate the maximum stream access point(SAP) interval of contained media streams. @startWithSAP attribute canindicate the number of media segments that start with an SAP.@maxPlayoutRate attribute can indicate the maximum playout rate.@codingDependency attribute can indicate presence or absence of at leastone access unit that depends on one or more other access units fordecoding. @scanType attribute can indicate the scan type of the sourcematerial of the video media component type. A FramePacking element canspecify frame-packing information of the video media component type. AnAudioChannelConfiguration element can specify the audio channelconfiguration of the audio media component type. A ContentProtectionelement can specify information about content protection schemes usedfor the associated representation. An EssentiaIProperty element canindicate information about an element that is essentially considered inprocessing. A SupplementalProperty element can specify supplementalinformation used to optimize processing. An InbandEventStream elementcan specify presence or absence of an inband event stream in theassociated representation. A Location element can specify information ona location at which the associated representation can be acquired. TheLocation element can include information about a broadcast stream orphysical channel data pipes carrying the associated representation. TheDASH client or the future broadcast reception apparatus can obtain theassociated representation using the Location element. That is, thereception apparatus of the future broadcast system can obtaininformation about the location of the associated representation usinglocation information included in the common attributes and elements ofthe MPD without using the aforementioned CMT and acquire the associatedrepresentation on the basis of the obtained information. Theaforementioned representation can be described as a component accordingto an embodiment.

In another embodiment, the future broadcast system can allocateinformation about a transport path, such as the associatedrepresentation, to a @servicelocation attribute of the base URL elementin the DASH MPD. The future broadcast system can enable the DASH clientto be aware of information about paths through which segments associatedwith the corresponding representation are delivered using@servicelocation attribute.

FIG. 75 illustrates transport session instance description according toan embodiment of the present invention. When an application layertransmission method corresponds to real-time object delivery overunidirectional transport (ROUTE), a ROUTE session can be composed of oneor more layered coding transport (LCT) sessions. Detailed informationabout one or more transport sessions can be signaled through transportsession instance description. In the case of ROUTE, the transportsession instance description may be referred to as LCT session instancedescription (LSID). Particularly, the transport session instancedescription can define what is delivered through each LCT transportsession constituting the ROUTE session. Each transport session can beuniquely identified by a transport session identifier (TSI). The TSI canbe included in an LCT header. The transport session instance descriptioncan describe all transport sessions carried by the correspondingsession. For example, LSID can describe all LCT sessions carried byROUTE. The transport session instance description may be deliveredthrough the same ROUTE session as transport sessions or through adifferent ROUTE session or unicast.

When delivered through the same ROUTE session, the transport sessioninstance description can be delivered through a transport session havinga TSI of 0. While an object referred to in the transport sessioninstance description may be delivered through the transport session withTSI=0, the object can have a TOI value different from that of thetransport session instance description. Otherwise, the object may bedelivered through a separate transport session with TSI≠0. The transportsession instance description can be updated using at least one of theversion number, validity information and expiration information. Thetransport session instance description can be represented in a bitstreamin addition to the illustrated format.

The transport session instance description can include version,validFrom and expiration attributes. For each transport session, thetransport session instance description can include a TSI attribute, aSourceFlow element, a RepairFlow element and a TransportSessionPropertyelement. The version attribute can indicate the version information ofthe transport session instance description, and the version informationcan increase whenever contents thereof are updated. Transport sessioninstance description having a highest version number is the currentlyvalid version. The validFrom attribute can indicate the data and timefrom which the corresponding transport session instance description isvalid. The validFrom attribute may not be included in the transportsession instance description according to embodiment. In this case, thereceiver can assume that the corresponding transport session instancedescription is valid immediately. The expiration attribute can indicatethe date and time when the corresponding transport session instancedescription expires. The expiration attribute may not be included in thetransport session instance description. In this case, the receiver canassume that the corresponding transport session instance description isvalid for all time. If transport session instance description having anexpiration attribute is received, the transport session instancedescription can conform to the corresponding expiration attribute. TheTSI attribute can indicate a transport session identifier. TheSourceFlow element provides information of a source flow transmittedwith the corresponding TSI. The SourceFlow element will be described indetail below. The RepairFlow element can provide information of a repairflow transmitted with the corresponding TSI. TheTransportSessionProperty element can provide additional propertyinformation about the corresponding transport session. The transportsession instance description can include additional property informationabout a transport session in the TransportSessionProperty element. Forexample, the additional information can include service signalinginformation about the transport session.

FIG. 76 illustrates shows a SourceFlow element of the future broadcastsystem according to an embodiment of the present invention. TheSourceflow element can include an EFDT element, an idRef attribute, arealtime attribute, a minBufferSize attribute, an Application Identifierelement, a PayloadFormat element and/or a SourceFlowProperty element.The EFDT element can specify detailed information of file delivery data.The EFDT element indicates an extended file delivery table (FDT)instance and will be described in detail below. The idRef attribute canindicate an EFDT identifier and can be represented as a URI by thecorresponding transport session. The realtime attribute can indicatethat corresponding LCT packets include extension headers. The extendedheaders can include timestamps indicating presentation time of anincluded delivery object. The minBufferSize attribute can define themaximum amount of data that needs to be stored in the receiver. TheApplication Identifier element can provide additional information thatcan be mapped to the application carried in the corresponding transportsession. For example, representation ID of DASH content or ApplicationSet parameters of a DASH representation can be provided as additionalinformation in order to select a transport session for rendering. ThePayloadFormat element can define payload formats of ROUTE packetscarrying objects of the source flow. The PayloadFormat element caninclude a codePoint attribute, a deliveryObjectFormat attribute, afragmentation attribute, a deliveryOrder attribute, a sourceFecPayloadIDattribute and/or an FECParameters element. The codePoint attribute candefine a code point used in the corresponding payload. This can indicatethe value of the CP field in the LCT header. The deliveryObjectFormatattribute can indicate the payload format of the corresponding deliveryobject. The fragmentation attribute can define the type offragmentation. The deliveryOrder attribute can indicate the order ofdelivery of objects. The sourceFecPayloadID attribute can define theformat of a source FEC payload identifier. The FECParameters element candefine FEC parameters. This includes an FEC encoding id, an instance id,etc. The SourceFlowProperty element can provide property informationabout the corresponding source flow. For example, the propertyinformation can include location information of a broadcast streamcarrying the corresponding source flow data. Here, the locationinformation of the broadcast stream may include information about a datapipe or physical layer pipe (PLP) in the broadcast stream.

FIG. 77 shows signaling data transmitted, by the future broadcast systemaccording to another embodiment of the present invention, for fastbroadcast service scan. Illustrated service acquisition information mayfurther include information about link layer signaling in addition tothe aforementioned service acquisition information. The informationabout link layer signaling can include flag information indicatingpresence of link layer signaling, version information of the link layersignaling data and information about a data pipe or a PLP through whichlink layer signaling is delivered. FIC information (service acquisitioninformation) for supporting fast broadcast service scan andservice/component acquisition can include information about anapplication layer transport session delivering service and componentdata. As illustrated, the service acquisition information can berepresented in a binary format. However, the FIC information may berepresented in other formats such as XML according to embodiments.

The service acquisition information can include the following fields. AnFIC_portocol_version field can indicate the version of the structure ofsignaling information. A TSID field can indicate the identifier of abroadcast stream. An FIC_data_version field can indicate the dataversion of the corresponding FIC information. An FIC_data_version fieldcan be increased when the contents of the FIC are changed. Anum_partitions field can indicate the number of partitions of abroadcast stream. It is assumed that each broadcast stream can bedivided into one or more partitions and transmitted in order to use thenum_partitions field. Each partition can include a plurality of DPs by asingle broadcaster. Each partition can indicate a part of a broadcaststeam, used by a single broadcaster. A partition_id field can indicatethe identifier of the corresponding partition. Apartition_protocol_version field can indicate the version of theaforementioned partition structure. A num_services field can indicatethe number of one or more components included in the correspondingpartition. A service_id field can indicate a service identifier. Aservice_data_version field can indicate a change of service loop data inthe FIC or a change of service signaling data associated with thecorresponding service. A service_data_version field can be increased by1 whenever included service data is changed. The receiver can detect aservice loop data change of the FIC or a change of signaling associatedwith the corresponding service using the service_data_version field. Achannel_number field can indicate the channel number associated with thecorresponding service. A service_category field can indicate thecategory of the corresponding service. For example, the service_categoryfield can indicate A/V, audio, ESG, CoD, etc. Ashort_service_name_length field can indicate the length of the name ofthe corresponding service. A short_service_name field can indicate thename of the corresponding service. A service_status field can indicatethe status of the corresponding service and represent an active orsuspended attribute and a hidden or shown attribute according to thevalue thereof. A service_distribution field can have an attributesimilar to “multi-ensemble” flag of ATSC M/H. For example, theservice_distribution field can indicate information about whether thecorresponding service is included in the corresponding partition, theservice is presentable only with the corresponding partition althoughthe service is partially included in the partition, another partition isnecessary for presentation, or other broadcast streams are necessary forpresentation. An sp_indicator field is a service protection flag and canindicate whether one or more components necessary for presentation areprotected. An IP_version_flag field can indicate the following IPaddress format. The IP_version_flag field can indicate that IPv4 is usedwhen the value thereof is 0 and can indicate that IPv6 is used when thevalue thereof is 1. A source_IP_address_flag field can indicate whetherthe FIC information includes source_IP_addr. The source_IP_address_flagfield can indicate presence of source_IP_addr when the value thereofis 1. A num_transport_session field can indicate the number of transportsessions (e.g. ROUTE or MMTP sessions) in which component data of thecorresponding service is transmitted in a broadcast stream. Asource_IP_addr field can indicate the source IP address of an IPdatagram including the component data of the corresponding service whenthe source_IP_address_flag is 1. A dest_IP_addr field can indicate thedestination IP address of the IP datagram including the component dataof the corresponding service. A dest_UDP_port field can indicate the UDPport number of the IP datagram including the component data of thecorresponding service. An LSID_DP field can indicate the identifier of adata pipe of a physical layer, which delivers signaling includingdetailed information about a transport session. In the case of ROUTE,for example, the signaling including the detailed information about thetransport session can be LCT session instance description includinginformation about an LCT transport session of a ROUTE session. AnLSID_tsi field can indicate the identifier of a transport sessionthrough which transport session instance description, which is signalingincluding detailed information about transport sessions, is transmitted.Here, the transport session instance description can be LSID in the caseof an LCT transmission session. In addition, signaling associated withthe corresponding service can be delivered through the transport sessionin which the transport session instance description is transmitted. Aservice_signaling_flag field can indicate whether service signaling istransmitted through the corresponding transport session. Theservice_signaling_flag field can indicate presence of a DP includingservice signaling when the value thereof is 1. A signaling_data_versionfield can indicate a change of related service signaling data. The valueof the signaling_data_version field can increase by 1 whenever theservice signaling data is changed. The receiver can detect a change ofsignaling related to the corresponding service using thesignaling_data_version field. A signaling_DP field can indicate theidentifier of a data pipe of the physical layer, which delivers servicesignaling. A signaling_tsi field can indicate the identifier of atransport session delivering service signaling. Alink_layer_signaling_flag field can indicate whether the serviceacquisition information carries link layer (or low layer) signaling. Alink_layer_signaling_data_version field can indicate a change ofassociated link layer (or low layer) signaling data. This field can beincreased by 1 whenever the link layer signaling data is changed. Thereceiver can detect variation in link layer (or low layer) signalingusing the link_layer_signaling_data_version field. Alink_layer_signaling_DP field can indicate the identifier of a physicallayer data pipe carrying link layer (or low layer) signaling that can beused in the L2 layer. A transport session descriptors field can includetransport session level descriptors. Each descriptor can be extended andinclude a num_descriptors field. Each descriptor can include as manydescriptor loops as the number indicated by the num_descriptors field.The transport session descriptors field can include transport sessionlevel descriptors. A service descriptors field can include service leveldescriptors. A partition descriptors field can include a partition leveldescriptor, and one partition can indicate part of broadcast streamsused by a single broadcaster. An FIC session descriptors field caninclude FIC level descriptors. According to an embodiment, the fieldsincluded in the FIC may be included in a table other than the FIC andtransmitted along with a broadcast signal.

FIG. 78 shows signaling data transmitted by the future broadcast systemaccording to another embodiment of the present invention for fastbroadcast service scan. FIC information (service acquisitioninformation) for supporting fast broadcast service scan andservice/component acquisition can include information about anapplication layer transport session delivering service and componentdata. The service acquisition information may further includeinformation about link layer signaling. As illustrated, the serviceacquisition information can be represented in a binary format. However,the FIC information may be represented in other formats such as XMLaccording to embodiments.

The service acquisition information can include the following fields. AnFIC_portocol_version field can indicate the version of the structure ofsignaling information. A num_partitions field can indicate the number ofpartitions of a broadcast stream. It is assumed that each broadcaststream can be divided into one or more partitions and transmitted inorder to use the num_partitions field. Each partition can include aplurality of DPs corresponding to a single broadcaster. Each partitioncan indicate a part of a broadcast steam, used by a single broadcaster.A partition_id field can indicate the identifier of the correspondingpartition. A partition_protocol_version field can indicate the versionof the aforementioned partition structure. A num_services field canindicate the number of one or more services included in thecorresponding partition. Each service can include a plurality ofsignaling tables. For example, each service can include DASH MPDincluding components and information about segments thereof, a CMTincluding identifiers of components included in broadband and otherbroadcast streams, an application signaling table (AST) and a URLsignaling table (UST) including at least one of the URLs of the MPD, CMTand AST. These signaling tables can be included in a signaling channelof the corresponding service. A service_id field can indicate a serviceidentifier. A service_data_version field can indicate a change ofservice loop data in the FIC or a change of service signaling dataassociated with the corresponding service. A service_data_version fieldcan be increased by 1 whenever included service data is changed. Forexample, service_data_version field can be increased by 1 when the FIC,MPD, CMT, AST or UST is changed. The receiver can detect a service loopdata change of the FIC or a change of signaling associated with thecorresponding service using the service_data_version field. Aservice_channel_number field can indicate the channel number associatedwith the corresponding service. A service_category field can indicatethe category of the corresponding service. For example, theservice_category field can indicate A/V, audio, ESG, CoD, etc. Ashort_service_name_length field can indicate the length of the name ofthe corresponding service. A short_service_name field can indicate thename of the corresponding service. A service_status field can indicatethe status of the corresponding service and represent an active orsuspended attribute and a hidden or shown attribute according to thevalue thereof. A service_distribution field can have an attributesimilar to “multi-ensemble” flag of ATSC M/H. For example, theservice_distribution field can indicate information about whether thecorresponding service is included in the corresponding partition, theservice is presentable only with the corresponding partition althoughthe service is partially included in the partition, another partition isnecessary for presentation, or other broadcast streams are necessary forpresentation. An sp_indicator field is a service protection flag and canindicate whether one or more components necessary for presentation areprotected. An IP_version_flag field can indicate the following IPaddress format. The IP_version_flag field can indicate that IPv4 is usedwhen the value thereof is 0 and indicate that IPv6 is used when thevalue thereof is 1. A num_ROUTE_sessions field can indicate the numberof transport sessions delivering component data of the correspondingservice in a broadcast stream. For example, transport session can beROUTE sessions. The following information can be set per ROUTE session.A source_IP_addr field can indicate the source IP address of an IPdatagram including the component data of the corresponding service. Adest_IP_addr field can indicate the destination IP address of the IPdatagram including the component data of the corresponding service. Adest_UDP_port field can indicate the UDP port number of the IP datagramincluding the component data of the corresponding service. An LSID_DPfield can indicate the identifier of a data pipe of a physical layer,which delivers signaling including detailed information about atransport session. In the case of ROUTE, for example, the signalingincluding the detailed information about the transport session can beLCT session instance description including information about an LCTtransport session of a ROUTE session. An LSID_tsi field can indicate theidentifier of a transport session through which transport sessioninstance description that is signaling including detailed informationabout transport sessions is transmitted. Here, the transport sessioninstance description can be LSID in the case of an LCT transmissionsession. In addition, signaling associated with the correspondingservice can be delivered through the transport session in which thetransport session instance description is transmitted. Acomponent_signaling_flag field can indicate whether service signaling ofthe corresponding service is transmitted through the correspondingtransport session. When the component_signaling_flag is 1, this canindicate that data transmitted through the corresponding transportsession includes service signaling (e.g. MPD (DASH Media PresentationDescription), CMT or the like). Here, the CMT is a component mappingtable and can include identifiers of components delivered throughbroadband and can also include information about components included inother broadcast streams. Each service can include service signalingchannels. The service signaling channels can include an MPD, a CMT, anAST and/or a UST. A service signaling channel may be a signaling channelfrom among a plurality of route sessions for services, and presence orabsence thereof can be indicated through the component signaling flag.When signaling and service components are transmitted through aplurality of transport sessions (ROUTE or MMTP sessions), theaforementioned service signaling tables can be preferably delivered by asingle transport session. A link_layer_signaling_flag field can indicatewhether the service acquisition information carries link layer (or lowlayer) signaling. A link_layer_signaling_data_version field can indicatea change of associated link layer (or low layer) signaling data. Thisfield can be increased by 1 whenever the link layer signaling data ischanged. The receiver can detect a variation in link layer (or lowlayer) signaling using the link_layer_signaling_data_version field. Alink_layer_signaling_DP field can indicate the identifier of a physicallayer data pipe carrying link layer (or low layer) signaling that can beused in the L2 layer.

A ROUTE session descriptors field can include transport session leveldescriptors. Each descriptor can be extended and include anum_descriptors field. Each descriptor can include as many descriptorloops as a number corresponding to a value indicated by thenum_descriptors field. A transport session descriptors field can includetransport session level descriptors. A service descriptors field caninclude service level descriptors. A partition descriptors field caninclude a partition level descriptor, and one partition can indicatepart of broadcast streams used by a single broadcaster. An FIC sessiondescriptors field can include FIC level descriptors.

According to an embodiment, the fields included in the FIC may beincluded in a table other than the FIC and transmitted along with abroadcast signal.

FIG. 79 illustrates a method for acquiring service layer signaling inthe future broadcast system according to an embodiment of the presentinvention. The upper part of the figure shows a service layer signalingformat used in the future broadcast system according to the presentinvention. Service layer signaling can be encapsulated in theillustrated format. For example, encapsulated service layer signalingcan include a Generic packet header (GPH), an IP packet header (IPH), aUDP datagram header (UDPH), an application transport protocol (e.g.ROUTE or MMTP) header (ATPH), a signaling message header (SMH) and asignaling message. When the future broadcast system uses theaforementioned service signaling, the future broadcast system candeliver the service signaling as shown in the lower part of the figure.A broadcast signal of the future broadcast system can be transmittedthrough physical layer frames. Broadcast signal frames can includephysical layer signaling. Physical layer signaling information caninclude a field with respect to fast service acquisition information.This field can include version information of the fast serviceacquisition information. In other words, the field can indicate whethera physical layer frame includes the fast service acquisition informationor whether the fast service acquisition information needs to be parsed.The receiver can acquire the fast service acquisition information usingthe field of physical layer signaling. A broadcast signal of the futurebroadcast system can include the fast service acquisition information ina physical layer frame. The fast service acquisition information mayinclude a service identifier and information about a data pipe or a PLPthrough which at least one of service layer signaling information and atransport session instance descriptor is delivered. That is, thereceiver can identify the PLP through which at least one of the servicelayer signaling information and transport session instance descriptor isdelivered using data pipe or PLP identifier information included in thefast service acquisition information and acquire the service layersignaling information or transport session instance descriptor includedtherein. As illustrated, the service layer signaling information or thetransport session instance descriptor can be delivered by a 0-thtransport session in the corresponding PLP. That is, the service layersignaling information can be delivered by the transport sessioncorresponding to tsi=0 in the PLP indicated by the PLP identifierincluded in the service acquisition information. In other words, theidentifier of the transport session through which service layersignaling is delivered can be fixed to 0.

As illustrated, the service layer signaling can be encapsulated asdescribed above. That is, the service layer signaling format can includea generic packet header (GPH), an IP packet header (IPH), a UDP datagramheader (UDPH), an application transport protocol (e.g. ROUTE or MMTP)header (ATPH), a signaling message header (SMH) and a signaling message.Here, the signaling message may include MPD delivery description,component mapping description or URL signaling description according totype of a message delivered by the service layer signaling.

In addition, the transport session instance descriptor can have theaforementioned encapsulation format, as illustrated. That is, thetransport session instance descriptor can include a generic packetheader (GPH), an IP packet header (IPH), a UDP datagram header (UDPH),an application transport protocol (e.g. ROUTE or MMTP) header (ATPH), asignaling message header (SMH) and a signaling message. Here, thesignaling message can include the transport session instance descriptor.In the present invention, the transport session instance descriptor maybe included in service layer signaling and delivered.

FIG. 80 illustrates a method for acquiring service layer signaling andlink layer signaling in the future broadcast system according to anembodiment of the present invention. When the future broadcast systemuses the aforementioned service layer signaling, the future broadcastsystem can deliver the service layer signaling as shown in the figure. Abroadcast signal of the future broadcast system can be transmittedthrough physical layer frames. Broadcast signal frames can includephysical layer signaling. Physical layer signaling information caninclude a field with respect to fast service acquisition information.This field can include version information of the fast serviceacquisition information. In other words, the field can indicate whethera physical layer frame includes the fast service acquisition informationor whether the fast service acquisition information needs to be parsed.The receiver can acquire the fast service acquisition information usingthe field of physical layer signaling. A broadcast signal of the futurebroadcast system can include the fast service acquisition information ina physical layer frame. The fast service acquisition information mayinclude a service identifier and information about a data pipe or a PLPthrough which at least one of service layer signaling information and atransport session instance descriptor is delivered. That is, thereceiver can identify the PLP through which at least one of the servicelayer signaling information and transport session instance descriptor isdelivered using data pipe or PLP identifier information included in thefast service acquisition information and acquire the service layersignaling information or transport session instance descriptor includedtherein. As illustrated, the service layer signaling information or thetransport session instance descriptor can be delivered by a 0-thtransport session in the corresponding PLP. That is, the service layersignaling information can be delivered by the transport sessioncorresponding to tsi=0 in the PLP indicated by the PLP identifierincluded in the service acquisition information. In other words, theidentifier of the transport session through which service layersignaling is delivered can be fixed to 0.

As illustrated, the service layer signaling can be encapsulated asdescribed above. That is, the service layer signaling format can includea generic packet header (GPH), an IP packet header (IPH), a UDP datagramheader (UDPH), an application transport protocol (e.g. ROUTE or MMTP)header (ATPH), a signaling message header (SMH) and a signaling message.Here, the signaling message may include MPD delivery description,component mapping description or URL signaling description according totype of a message delivered by the service layer signaling.

In addition, the transport session instance descriptor can have theaforementioned encapsulation format, as illustrated. That is, thetransport session instance descriptor can include a generic packetheader (GPH), an IP packet header (IPH), a UDP datagram header (UDPH),an application transport protocol (e.g. ROUTE or MMTP) header (ATPH), asignaling message header (SMH) and a signaling message. Here, thesignaling message can include the transport session instance descriptor.In the present invention, the transport session instance descriptor maybe included in service layer signaling and delivered.

In addition, the fast service acquisition information may includeinformation about a data pipe or a PLP through which link layersignaling is delivered. That is, the receiver can identify the PLPthrough which the link layer signaling is delivered using data pipe orPLP identifier information included in the fast service acquisitioninformation and acquire the link layer signaling included therein. Asillustrated, a transport link layer signaling format can include aGeneric packet header (GPH) and a signaling message. The signalingmessage can include information about link layer signaling. The receivercan acquire link layer signaling (or low layer signaling) through a datapipe and obtain service/component signaling such as a component mappingtable through the application transport protocol.

FIG. 81 illustrates a method for acquiring service layer signaling inthe future broadcast system according to an embodiment of the presentinvention. When the future broadcast system uses 3GPP eMBMS signalingfor service/component signaling, the future broadcast system can deliverthe signaling as shown in the figure. Here, service layer signaling caninclude User Service Bundle Description (USBD), MPD, Session DescriptionProtocol and may further include transport session instance description.A broadcast signal of the future broadcast system can be transmittedthrough physical layer frames. Broadcast signal frames can includephysical layer signaling. Physical layer signaling information caninclude a field with respect to fast service acquisition information.This field can include version information of the fast serviceacquisition information. In other words, the field can indicate whethera physical layer frame includes the fast service acquisition informationor whether the fast service acquisition information needs to be parsed.The receiver can acquire the fast service acquisition information usingthe field of physical layer signaling. A broadcast signal of the futurebroadcast system can include the fast service acquisition information ina physical layer frame. The fast service acquisition information mayinclude a service identifier and information about a data pipe or a PLPthrough which at least one of service layer signaling information and atransport session instance descriptor is delivered. That is, thereceiver can identify the PLP through which at least one of the servicelayer signaling information and transport session instance descriptor isdelivered using data pipe or PLP identifier information included in thefast service acquisition information and acquire the service layersignaling information or transport session instance descriptor includedtherein. As illustrated, the service layer signaling information or thetransport session instance descriptor can be delivered by a 0-thtransport session in the corresponding PLP. That is, the service layersignaling information can be delivered by the transport sessioncorresponding to tsi=0 in the PLP indicated by the PLP identifierincluded in the service acquisition information. In other words, theidentifier of the transport session through which service layersignaling is delivered can be fixed to 0.

As illustrated, the service layer signaling can be encapsulated asdescribed above. That is, the service layer signaling format can includea generic packet header (GPH), an IP packet header (IPH), a UDP datagramheader (UDPH), an application transport protocol (e.g. ROUTE or MMTP)header (ATPH), a signaling message header (SMH) and a signaling message.Here, the signaling message may include MPD delivery description,component mapping description or URL signaling description according totype of a message delivered by the service layer signaling.

In addition, the transport session instance descriptor can have theaforementioned encapsulation format, as illustrated. That is, thetransport session instance descriptor can include a generic packetheader (GPH), an IP packet header (IPH), a UDP datagram header (UDPH),an application transport protocol (e.g. ROUTE or MMTP) header (ATPH), asignaling message header (SMH) and a signaling message. Here, thesignaling message can include the transport session instance descriptor.In the present invention, the transport session instance descriptor maybe included in service layer signaling and delivered.

FIG. 82 illustrates a method for acquiring service layer signaling andlink layer signaling in the future broadcast system according to anembodiment of the present invention. When the future broadcast systemuses 3GPP eMBMS signaling, the future broadcast system can deliver thesignaling as shown in the figure. A broadcast signal of the futurebroadcast system can be transmitted through physical layer frames.Broadcast signal frames can include physical layer signaling. Physicallayer signaling information can include a field with respect to fastservice acquisition information. This field can include versioninformation of the fast service acquisition information. In other words,the field can indicate whether a physical layer frame includes the fastservice acquisition information or whether the fast service acquisitioninformation needs to be parsed. The receiver can acquire the fastservice acquisition information using the corresponding field ofphysical layer signaling. A broadcast signal of the future broadcastsystem can include the fast service acquisition information in aphysical layer frame. The fast service acquisition information mayinclude a service identifier and information about a data pipe or a PLPthrough which at least one of service layer signaling information and atransport session instance descriptor is delivered. That is, thereceiver can identify the PLP through which at least one of the servicelayer signaling information and transport session instance descriptor isdelivered using data pipe or PLP identifier information included in thefast service acquisition information and acquire the service layersignaling information or transport session instance descriptor includedtherein. As illustrated, the service layer signaling information or thetransport session instance descriptor can be delivered by a 0-thtransport session in the corresponding PLP. That is, the service layersignaling information can be delivered by the transport sessioncorresponding to tsi=0 in the PLP indicated by the PLP identifierincluded in the service acquisition information. In other words, theidentifier of the transport session through which service layersignaling is delivered can be fixed to 0.

As illustrated, the service layer signaling can be encapsulated asdescribed above. That is, the service layer signaling format can includea generic packet header (GPH), an IP packet header (IPH), a UDP datagramheader (UDPH), an application transport protocol (e.g. ROUTE or MMTP)header (ATPH), a signaling message header (SMH) and a signaling message.Here, the signaling message may include MPD delivery description,component mapping description or URL signaling description according totype of a message delivered by the service layer signaling.

In addition, the transport session instance descriptor can have theaforementioned encapsulation format, as illustrated. That is, thetransport session instance descriptor can include a generic packetheader (GPH), an IP packet header (IPH), a UDP datagram header (UDPH),an application transport protocol (e.g. ROUTE or MMTP) header (ATPH), asignaling message header (SMH) and a signaling message. Here, thesignaling message can include the transport session instance descriptor.In the present invention, the transport session instance descriptor maybe included in service layer signaling and delivered.

In addition, the fast service acquisition information may includeinformation about a data pipe or a PLP through which link layersignaling is delivered. That is, the receiver can identify the PLPthrough which the link layer signaling is delivered using data pipe orPLP identifier information included in the fast service acquisitioninformation and acquire the link layer signaling included therein. Asillustrated, a transport link layer signaling format can include ageneric packet header (GPH) and a signaling message. The signalingmessage can include information about link layer signaling. The receivercan acquire link layer signaling (or low layer signaling) through a datapipe and obtain service/component signaling such as a component mappingtable through the application transport protocol. That is, the futurebroadcast system can include, in physical layer frames, signalinginformation about a data pipe or a PLP including link layer signaling.

FIG. 83 illustrates a method for delivering service layer signaling inthe future broadcast system according to an embodiment of the presentinvention. The upper part of the figure shows a service layer signalingformat used in the future broadcast system of the present invention.Service layer signaling can be encapsulated in the illustrated format.For example, encapsulated service layer signaling can be composed of acombination of a generic packet header (GPH), an IP packet header (IPH),a UDP datagram header (UDPH), an application transport protocol (e.g.ROUTE or MMTP) header (ATPH) and a signaling message, as shown in theleft upper part of the figure. Alternatively, encapsulated service layersignaling can be composed of a combination of a generic packet header(GPH), an IP packet header (IPH), a UDP datagram header (UDPH), anapplication transport protocol (e.g. ROUTE or MMTP) header (ATPH), asignaling message header (SMH) and a signaling message, as shown in theright upper part of the figure. The ATPH may include a filtering indexwith respect to the service layer signaling. Here, the filtering indexcan include a signaling id, a version, etc. The signaling id can includeidentifier information about service layer signaling and the version canindicate the version of information included in the service layersignaling.

When the future broadcast system uses the aforementioned servicesignaling, the future broadcast system can deliver the service signalingas shown in the lower part of the figure. A broadcast signal of thefuture broadcast system can be transmitted through physical layerframes. Broadcast signal frames can include physical layer signaling.Physical layer signaling information can include a field with respect tofast service acquisition information. This field can include versioninformation of the fast service acquisition information. In other words,the field can indicate whether a physical layer frame includes the fastservice acquisition information or whether the fast service acquisitioninformation needs to be parsed. The receiver can acquire the fastservice acquisition information using the corresponding field ofphysical layer signaling. A broadcast signal of the future broadcastsystem can include the fast service acquisition information in aphysical layer frame. The fast service acquisition information mayinclude a service identifier and information about a data pipe or a PLPthrough which at least one of service layer signaling information and atransport session instance descriptor is delivered. That is, thereceiver can identify the PLP through which at least one of the servicelayer signaling information and transport session instance descriptor isdelivered using data pipe or PLP identifier information included in thefast service acquisition information and acquire the service layersignaling information or transport session instance descriptor includedtherein. As illustrated, the service layer signaling information or thetransport session instance descriptor can be delivered by a 0-thtransport session in the corresponding PLP. That is, the service layersignaling information can be delivered by the transport sessioncorresponding to tsi=0 in the PLP indicated by the PLP identifierincluded in the service acquisition information. In other words, theidentifier of the transport session through which service layersignaling is delivered can be fixed to 0.

As illustrated, the service layer signaling can be encapsulated asdescribed above. That is, the service layer signaling format can includea generic packet header (GPH), an IP packet header (IPH), a UDP datagramheader (UDPH), an application transport protocol (e.g. ROUTE or MMTP)header (ATPH), a signaling message header (SMH) and a signaling message.Here, the signaling message may include MPD delivery description,component mapping description or URL signaling description according totype of a message delivered by the service layer signaling. As describedabove, the ATPH can include the filtering index with respect to theservice layer signaling. Here, the filtering index can include asignaling id, a version, etc. The signaling id can include identifierinformation about service layer signaling and the version can indicatethe version of information included in the service layer signaling. Forexample, service layer signaling including MPD delivery description canhave a value of 0xF1 as the signaling id thereof and a value of 0x01 asthe version information thereof. The version information can be changedwhen the contents of the MPD delivery description corresponding to thesignaling message of the corresponding service layer signaling ischanged. Service layer signaling including component mapping descriptioncan have a value of 0xF2 as the signaling id thereof and a value of 0x01as the version information thereof. The version information can bechanged when the contents of the component mapping descriptioncorresponding to the signaling message of the corresponding servicelayer signaling is changed. Service layer signaling including URLsignaling description can have a value of 0xF3 as the signaling idthereof and a value of 0x01 as the version information thereof. Theversion information can be changed when the contents of the URLsignaling description corresponding to the signaling message of thecorresponding service layer signaling are changed. Accordingly, thereceiver can filter desired service layer signaling using signaling idand version information corresponding to filtering information includedin the application transport protocol header of the service layersignaling. For example, when the receiver intends to receive the MPDdelivery description, the receiver can receive the service layersignaling having a signaling id of 0xF1. In addition, the receiver cancheck the version information and, only when the MPD deliverydescription has been updated from the previously received MPD deliverydescription, parse the corresponding service layer signaling.Accordingly, the receiver can reduce unnecessary parsing operation withrespect to service layer signaling and decrease processing overhead. Asdescribed above, the future broadcast system can support the receiversuch that the receiver can filter desired information by including, inthe transport protocol header of service layer signaling, signaling IDand version information.

FIG. 84 illustrates a method for transmitting service layer signalingand link layer signaling in the future broadcast system according to anembodiment of the present invention. Service layer signaling used in thefuture broadcast system of the present invention can be encapsulated.For example, encapsulated service layer signaling can be composed of acombination of a generic packet header (GPH), an IP packet header (IPH),a UDP datagram header (UDPH), an application transport protocol (e.g.ROUTE or MMTP) header (ATPH) and a signaling message. Otherwise,encapsulated service layer signaling can be composed of a combination ofa generic packet header (GPH), an IP packet header (IPH), a UDP datagramheader (UDPH), an application transport protocol (e.g. ROUTE or MMTP)header (ATPH), a signaling message header (SMH) and a signaling message.The ATPH can include a filtering index with respect to the service layersignaling. Here, the filtering index can include a signaling id and aversion. The signaling id is identifier information about the servicelayer signaling and the version indicates the version of informationincluded in the service layer signaling.

When the future broadcast system uses the aforementioned servicesignaling, the future broadcast system can deliver the service signalingas illustrated in the figure. A broadcast signal of the future broadcastsystem can be transmitted through physical layer frames. Broadcastsignal frames can include physical layer signaling. Physical layersignaling information can include a field with respect to fast serviceacquisition information. This field can include version information ofthe fast service acquisition information. In other words, the field canindicate whether a physical layer frame includes the fast serviceacquisition information or whether the fast service acquisitioninformation needs to be parsed. The receiver can acquire the fastservice acquisition information using the field of physical layersignaling. A broadcast signal of the future broadcast system can includethe fast service acquisition information in a physical layer frame. Thefast service acquisition information may include a service identifierand information about a data pipe or a PLP through which at least one ofservice layer signaling information and a transport session instancedescriptor is delivered. That is, the receiver can identify the PLPthrough which at least one of the service layer signaling informationand transport session instance descriptor is delivered using data pipeor PLP identifier information included in the fast service acquisitioninformation and acquire the service layer signaling information ortransport session instance descriptor included therein. As illustrated,the service layer signaling information or the transport sessioninstance descriptor can be delivered by a 0-th transport session in thecorresponding PLP. That is, the service layer signaling information canbe delivered by the transport session corresponding to tsi=0 in the PLPindicated by the PLP identifier included in the service acquisitioninformation. In other words, the identifier of the transport sessionthrough which service layer signaling is delivered can be fixed to 0.

As illustrated, the service layer signaling can be encapsulated asdescribed above. That is, the service layer signaling format can includea generic packet header (GPH), an IP packet header (IPH), a UDP datagramheader (UDPH), an application transport protocol (e.g. ROUTE or MMTP)header (ATPH), a signaling message header (SMH) and a signaling message.Here, the signaling message may include MPD delivery description,component mapping description or URL signaling description according totype of a message delivered by the service layer signaling. As describedabove, the ATPH can include the filtering index with respect to theservice layer signaling. Here, the filtering index can include asignaling id, a version, etc. The signaling id can include identifierinformation about service layer signaling and the version can indicatethe version of information included in the service layer signaling. Forexample, service layer signaling including MPD delivery description canhave a value of 0xF1 as the signaling id thereof and a value of 0x01 asthe version information thereof. The version information can be changedwhen the contents of the MPD delivery description corresponding to thesignaling message of the corresponding service layer signaling arechanged. Service layer signaling including component mapping descriptioncan have a value of 0xF2 as the signaling id thereof and a value of 0x01as the version information thereof. The version information can bechanged when the contents of the component mapping descriptioncorresponding to the signaling message of the corresponding servicelayer signaling are changed. Service layer signaling including URLsignaling description can have a value of 0xF3 as the signaling idthereof and has a value of 0x01 as the version information thereof. Theversion information can be changed when the contents of the URLsignaling description corresponding to the signaling message of thecorresponding service layer signaling is changed. Accordingly, thereceiver can filter desired service layer signaling using signaling idand version information corresponding to filtering information includedin the application transport protocol header of the service layersignaling. For example, when the receiver intends to receive the MPDdelivery description, the receiver can receive the service layersignaling having a signaling id of 0xF1. In addition, the receiver cancheck the version information and, only when the MPD deliverydescription has been updated from the previously received MPD deliverydescription, parse the corresponding service layer signaling.Accordingly, the receiver can reduce unnecessary parsing operation withrespect to service layer signaling and decrease processing overhead. Asdescribed above, the future broadcast system can support the receiversuch that the receiver can filter desired information by including, inthe transport protocol header of service layer signaling, signaling IDand version information.

In addition, the fast service acquisition information may includeinformation about a data pipe or a PLP through which link layersignaling is delivered. That is, the receiver can identify the PLPthrough which the link layer signaling is delivered using data pipe orPLP identifier information included in the fast service acquisitioninformation and acquire the link layer signaling included therein. Asillustrated, a transport link layer signaling format can include ageneric packet header (GPH) and a signaling message. The signalingmessage can include information about link layer signaling. The receivercan acquire link layer signaling (or low layer signaling) through a datapipe and obtain service/component signaling such as a component mappingtable through the application transport protocol. That is, the futurebroadcast system can include, in physical layer frames, signalinginformation about a data pipe or a PLP including link layer signaling.

FIG. 85 illustrates a method for delivering service layer signaling inthe future broadcast system according to an embodiment of the presentinvention. Service layer signaling used in the future broadcast systemof the present invention can be encapsulated. For example, encapsulatedservice layer signaling can be composed of a combination of a genericpacket header (GPH), an IP packet header (IPH), a UDP datagram header(UDPH), an application transport protocol (e.g. ROUTE or MMTP) header(ATPH) and a signaling message. Otherwise, encapsulated service layersignaling can be composed of a combination of a generic packet header(GPH), an IP packet header (IPH), a UDP datagram header (UDPH), anapplication transport protocol (e.g. ROUTE or MMTP) header (ATPH), asignaling message header (SMH) and a signaling message. The ATPH caninclude a filtering index with respect to the service layer signaling.Here, the filtering index can include a signaling id and a version. Thesignaling id is identifier information about the service layer signalingand the version indicates the version of information included in theservice layer signaling.

When the future broadcast system uses 3GPP eMBMS signaling, thesignaling can be delivered as illustrated. When the future broadcastsystem uses the aforementioned service signaling, the service signalingcan be delivered as shown in the lower part of the figure. A broadcastsignal of the future broadcast system can be transmitted throughphysical layer frames. Broadcast signal frames can include physicallayer signaling. Physical layer signaling information can include afield with respect to fast service acquisition information. This fieldcan include version information of the fast service acquisitioninformation. In other words, the field can indicate whether a physicallayer frame includes the fast service acquisition information or whetherthe fast service acquisition information needs to be parsed. Thereceiver can acquire the fast service acquisition information using thefield of physical layer signaling. A broadcast signal of the futurebroadcast system can include the fast service acquisition information ina physical layer frame. The fast service acquisition information mayinclude a service identifier and information about a data pipe or a PLPthrough which at least one of service layer signaling information and atransport session instance descriptor is delivered. That is, thereceiver can identify the PLP through which at least one of the servicelayer signaling information and transport session instance descriptor isdelivered using data pipe or PLP identifier information included in thefast service acquisition information and acquire the service layersignaling information or transport session instance descriptor includedtherein. As illustrated, the service layer signaling information or thetransport session instance descriptor can be delivered by a 0-thtransport session in the corresponding PLP. That is, the service layersignaling information can be delivered by the transport sessioncorresponding to tsi=0 in the PLP indicated by the PLP identifierincluded in the service acquisition information. In other words, theidentifier of the transport session through which service layersignaling is delivered can be fixed to 0.

As illustrated, the service layer signaling can be encapsulated asdescribed above. That is, the service layer signaling format can includea generic packet header (GPH), an IP packet header (IPH), a UDP datagramheader (UDPH), an application transport protocol (e.g. ROUTE or MMTP)header (ATPH), a signaling message header (SMH) and a signaling message.Here, the signaling message may include User Service Bundle Description(USBD), MPD and Session Description Protocol according to type of amessage delivered by the service layer signaling. As described above,the ATPH can include the filtering index with respect to the servicelayer signaling. Here, the filtering index can include a signaling id, aversion, etc. The signaling id can include identifier information aboutservice layer signaling and the version can indicate the version ofinformation included in the service layer signaling. For example,service layer signaling including the User Service Bundle Descriptioncan have a value of 0xF4 as the signaling id thereof and a value of 0x01as the version information thereof. The version information can bechanged when the contents of the User Service Bundle Descriptioncorresponding to the signaling message of the corresponding servicelayer signaling are changed. Service layer signaling including theSession Description Protocol can have a value of 0xF5 as the signalingid thereof and a value of 0x01 as the version information thereof. Theversion information can be changed when the contents of the SessionDescription Protocol corresponding to the signaling message of thecorresponding service layer signaling are changed. Service layersignaling including the MPD can have a value of 0xF6 as the signaling idthereof and a value of 0x02 as the version information thereof. Theversion information can be changed when the contents of the MPDcorresponding to the signaling message of the corresponding servicelayer signaling are changed. Accordingly, the receiver can filterdesired service layer signaling using signaling id and versioninformation corresponding to filtering information included in theapplication transport protocol header of the service layer signaling.For example, when the receiver intends to receive the User ServiceBundle Description, the receiver can receive the service layer signalinghaving a signaling id of 0xF4. In addition, the receiver can check theversion information and, only when the User Service Bundle Descriptionhas been updated from the previously received User Service BundleDescription, parse the corresponding service layer signaling.Accordingly, the receiver can reduce unnecessary parsing operation withrespect to service layer signaling and decrease processing overhead. Asdescribed above, the future broadcast system can support the receiversuch that the receiver can filter desired information by including, inthe transport protocol header of service layer signaling, signaling IDand version information.

FIG. 86 illustrates a method for transmitting service layer signalingand link layer signaling in the future broadcast system according to anembodiment of the present invention. Service layer signaling used in thefuture broadcast system of the present invention can be encapsulated.For example, encapsulated service layer signaling can be composed of acombination of a generic packet header (GPH), an IP packet header (IPH),a UDP datagram header (UDPH), an application transport protocol (e.g.ROUTE or MMTP) header (ATPH) and a signaling message. Otherwise,encapsulated service layer signaling can be composed of a combination ofa generic packet header (GPH), an IP packet header (IPH), a UDP datagramheader (UDPH), an application transport protocol (e.g. ROUTE or MMTP)header (ATPH), a signaling message header (SMH) and a signaling message.The ATPH can include a filtering index with respect to the service layersignaling. Here, the filtering index can include a signaling id and aversion. The signaling id is identifier information about the servicelayer signaling and the version indicates the version of informationincluded in the service layer signaling.

When the future broadcast system uses 3GPP eMBMS signaling, thesignaling can be delivered as illustrated in the figure. A broadcastsignal of the future broadcast system can be transmitted throughphysical layer frames. Broadcast signal frames can include physicallayer signaling. Physical layer signaling information can include afield with respect to fast service acquisition information. This fieldcan include version information of the fast service acquisitioninformation. In other words, the field can indicate whether a physicallayer frame includes the fast service acquisition information or whetherthe fast service acquisition information needs to be parsed. Thereceiver can acquire the fast service acquisition information using thecorresponding field of physical layer signaling. A broadcast signal ofthe future broadcast system can include the fast service acquisitioninformation in a physical layer frame. The fast service acquisitioninformation may include a service identifier and information about adata pipe or a PLP through which at least one of service layer signalinginformation and a transport session instance descriptor is delivered.That is, the receiver can identify the PLP through which at least one ofthe service layer signaling information and transport session instancedescriptor is delivered using data pipe or PLP identifier informationincluded in the fast service acquisition information and acquire theservice layer signaling information or transport session instancedescriptor included therein. As illustrated, the service layer signalinginformation or the transport session instance descriptor can bedelivered by a 0-th transport session in the corresponding PLP. That is,the service layer signaling information can be delivered by thetransport session corresponding to tsi=0 in the PLP indicated by the PLPidentifier included in the service acquisition information. In otherwords, the identifier of the transport session through which servicelayer signaling is delivered can be fixed to 0.

As illustrated, the service layer signaling can be encapsulated asdescribed above. That is, the service layer signaling format can includea generic packet header (GPH), an IP packet header (IPH), a UDP datagramheader (UDPH), an application transport protocol (e.g. ROUTE or MMTP)header (ATPH), a signaling message header (SMH) and a signaling message.Here, the signaling message may include User Service Bundle Description(USBD), MPD and Session Description Protocol according to type of amessage delivered by the service layer signaling. As described above,the ATPH can include the filtering index with respect to the servicelayer signaling. Here, the filtering index can include a signaling id, aversion, etc. The signaling id can include identifier information aboutservice layer signaling and the version can indicate the version ofinformation included in the service layer signaling. For example,service layer signaling including the User Service Bundle Descriptioncan have a value of 0xF4 as the signaling id thereof and a value of 0x01as the version information thereof. The version information can bechanged when the contents of the User Service Bundle Descriptioncorresponding to the signaling message of the corresponding servicelayer signaling are changed. Service layer signaling including theSession Description Protocol can have a value of 0xF5 as the signalingid thereof and a value of 0x01 as the version information thereof. Theversion information can be changed when the contents of the SessionDescription Protocol corresponding to the signaling message of thecorresponding service layer signaling are changed. Service layersignaling including the MPD can have a value of 0xF6 as the signaling idthereof and a value of 0x02 as the version information thereof. Theversion information can be changed when the contents of the MPDcorresponding to the signaling message of the corresponding servicelayer signaling are changed. Accordingly, the receiver can filterdesired service layer signaling using signaling id and versioninformation corresponding to filtering information included in theapplication transport protocol header of the service layer signaling.For example, when the receiver intends to receive the User ServiceBundle Description, the receiver can receive the service layer signalinghaving a signaling id of 0xF4. In addition, the receiver can check theversion information and, only when the User Service Bundle Descriptionhas been updated from the previously received User Service BundleDescription, parse the corresponding service layer signaling.Accordingly, the receiver can reduce unnecessary parsing operation withrespect to service layer signaling and decrease processing overhead. Asdescribed above, the future broadcast system can support the receiversuch that the receiver can filter desired information by including, inthe transport protocol header of service layer signaling, signaling IDand version information.

In addition, the fast service acquisition information may includeinformation about a data pipe or a PLP through which link layersignaling is delivered. That is, the receiver can identify the PLPthrough which the link layer signaling is delivered using data pipe orPLP identifier information included in the fast service acquisitioninformation and acquire the link layer signaling included therein. Asillustrated, a transport link layer signaling format can include ageneric packet header (GPH) and a signaling message. The signalingmessage can include information about link layer signaling. The receivercan acquire link layer signaling (or low layer signaling) through a datapipe and obtain service/component signaling such as a component mappingtable through the application transport protocol. That is, the futurebroadcast system can include, in physical layer frames, signalinginformation about a data pipe or a PLP including link layer signaling.

FIG. 87 illustrates a method for transmitting service layer signaling ofthe future broadcast system according to an embodiment of the presentinvention. Service layer signaling may include the aforementionedsignaling or 3GPP eMBMS signaling. When a fast information channel isnot present in a broadcast signal of the future broadcast system,signaling data for supporting fast service scan and acquisition can betransmitted through a common data pipe, a data pipe or a PLP in aphysical frame as illustrated. In this case, the signaling dataassociated with fast service scan and acquisition can be encapsulated inthe form of link (or low) layer signaling and transmitted along withother link (or low) layer signaling. That is, the PLP in the frame cancarry the signaling data including service acquisition information.Furthermore, the signaling data may be transmitted through the same datapipe or PLP as that used to transmit service/component signaling orcomponent data or a separate data pipe or PLP. As the service/componentsignaling, the aforementioned signaling or 3GPP eMBMS signaling may betransmitted. The corresponding signaling can include a generic packetheader (GPH), an IP packet header (IPH), a UDP datagram header (UDPH),an application transport protocol (e.g. ROUTE or MMTP) header (ATPH), asignaling message header (SMH) and a signaling message, as describedabove. Here, the SMH may not be included in the signaling formataccording to an embodiment. The ATPH can include a filtering index withrespect to service layer signaling. Here, the filtering index caninclude a signaling id and a version. The signaling id is identifierinformation about the service layer signaling and the version indicatesthe version of information included in the service layer signaling.

The lower part of the figure shows a method for acquiring service layersignaling using service acquisition information included in link layersignaling. A PLP of a broadcast signal frame can include link layersignaling. The link layer signaling can include the aforementioned fastservice scan and acquisition information. The fast service scan andacquisition information can include a service identifier and PLPidentifier information including service layer signaling with respect tothe corresponding service. The PLP indicated by the corresponding PLPidentifier can include service layer signaling. The service layer caninclude a generic packet header (GPH), an IP packet header (IPH), a UDPdatagram header (UDPH), an application transport protocol (e.g. ROUTE orMMTP) header (ATPH), a signaling message header (SMH) and a signalingmessage. The signaling message of the service layer signaling caninclude transport session instance description, MPD deliverydescription, component mapping description or URL signaling description.The future broadcast signal receiver can acquire a desired service byparsing the service layer signaling.

FIG. 88 illustrates a method for delivering service layer signaling ofthe future broadcast system according to an embodiment of the presentinvention. Service layer signaling may include the aforementionedsignaling or 3GPP eMBMS signaling. A PLP of a broadcast signal frame caninclude link layer signaling. The link layer signaling can include theaforementioned fast service scan and acquisition information. The fastservice scan and acquisition information can include a serviceidentifier and PLP identifier information including service layersignaling with respect to the corresponding service. The PLP indicatedby the corresponding PLP identifier can include service layer signaling.The service layer can include a generic packet header (GPH), an IPpacket header (IPH), a UDP datagram header (UDPH), an applicationtransport protocol (e.g. ROUTE or MMTP) header (ATPH) and a signalingmessage. The signaling message of the service layer signaling caninclude transport session instance description, MPD deliverydescription, component mapping description or URL signaling description.The future broadcast signal receiver can acquire a desired service byparsing the service layer signaling. Here, the ATPH can include afiltering index with respect to service layer signaling. Here, thefiltering index can include a signaling id and a version. The signalingid is identifier information about the service layer signaling and theversion indicates the version of information included in the servicelayer signaling. The method for filtering the service layer signalingusing the filtering index has been described above.

FIG. 89 illustrates a syntax of a header of a signaling messageaccording to another embodiment of the present invention.

The signaling message according to another embodiment of the presentinvention can be represented in XML. Here, signaling informationincluded in the signaling message in XML may correspond to the signalinginformation as described above or below.

The header of the signaling message according to another embodiment ofthe present invention can include signaling_id, signaling_length,signaling_id_extension, version_number, current_next_indicator,indicator_flags, fragmentation_indicator, payload_format_indicator,expiration_indicator, validfrom_indicator, fragment_number,last_fragment_number, payload_format, validfrom and/or expirationinformation.

For description of signaling information having names identical orsimilar to those of the signaling information included in theaforementioned signaling message header, from among the signalinginformation included in the signaling message header according to thepresent embodiment, refer to the above description.

The validfrom_indicator information indicates whether the signalingmessage header part includes a value of validfrom information. Forexample, a validfrom_indicator information value of 1 can indicate thatthe signaling message header part includes the validfrom information.

The validfrom information can indicate the time from which the signalingmessage included in a payload is available. The receiver can recognizethe time from which the signaling message included in the payload isavailable using the validfrom information and use the data included inthe payload as signaling information from the corresponding time.

Here, the payload refers to a region in a broadcast signal includingdata of broadcast services or broadcast content data (broadcast servicedata). That is, signaling information is generally transmitted through aregion, which is physically or logically separated from broadcastservice data, in a broadcast signal. According to the present invention,however, the signaling information can be transmitted through a payloadregion in a broadcast signal when the payload has a spare region orsignaling information, which exceeds a region allocated for signalinginformation transmission, needs to be transmitted.

FIG. 90 illustrates a protocol stack for processing a DASHinitialization segment according to an embodiment of the presentinvention.

The DASH initialization segment can be transmitted in the same format asthe aforementioned initialization segment delivery table or in XML.

The DASH initialization segment includes metadata (signalinginformation) necessary to represent media streams (broadcast signals)encapsulated into a plurality of segments. Here, a segment is a dataunit associated with HTTP-URL. A segment includes data for broadcastservices or broadcast content. Representation is a data unit includingone or more media streams in a transport format. The representation caninclude one or more segments.

The DASH initialization segment can be processed according to theillustrated protocol stack in the transmitter or the receiver. The DASHinitialization segment can be transmitted through one or more paths onthe protocol stack.

In the protocol stack, signaling information or broadcast service datacan be processed according to protocols of multiple layers. In thefigure, a signaling channel and data pipes may correspond to the firstlayer, an FIC and link layer frames may correspond to the second layer,Internet protocol (IP) may correspond to the third layer, a userdatagram protocol (UDP) may correspond to the fourth layer and ROUTE maycorrespond to the fifth layer. A link layer frame may include a linklayer packet described in the specification.

In the protocol stack processing the DASH initialization segment, whensignaling data such as the initialization segment is directly loaded inIP/IUDP and transmitted through the illustrated path (1), theinitialization segment may be transmitted as information in the formatof the aforementioned initialization segment delivery table or theinitialization segment itself may be transmitted in the form of an IPdatagram through processing of the protocol stack. The aforementionedinformation for service signaling and/or component signaling may also betransmitted through the path (1).

According to an embodiment of the present invention, the DASHinitialization segment can be transmitted along with media data througha specific session for transmitting signaling data, such as a path (2),or through a session for transmitting component data, such as a path(3). For example, the application transport protocol can use real-timeobject delivery over unidirectional transport (ROUTE). A ROUTE sessionmay include a session for transmitting signaling information and/or asession for transmitting broadcast media data. The broadcast systemfixes the TSI of a session for transmitting signaling information to aspecific value such that the receiver can recognize that datatransmitted through the session corresponding to the TSI is signalinginformation.

When the signaling information (data) such as the initialization segmentis transmitted through the illustrated path (2) and/or path (3),information indicating locations of data in the aforementioned signalingmessage format and the initialization segment in a transport stream or atransport object and/or information for identifying the data in thesignaling message format or the initialization segment from among datatransmitted along therewith can be provided in the form of fields in atransport protocol packet or separate signaling information.

FIG. 91 shows part of layered coding transport (LCT) session instancedescription (LSID) according to an embodiment of the present invention.

The LCT session instance descriptor can provide information indicatinglocations of data in the aforementioned signaling message format and theinitialization segment in a broadcast signal and/or information foridentifying the data in the signaling message format or theinitialization segment from among data transmitted along therewith canbe provided in the form of fields in a transport protocol packet orseparate signaling information.

The LCT session instance descriptor can include a PayloadFormat element.The PayloadFormat element can include @codePoint, @deliveryObjectFormat,@fragmentation, @deliveryOrder and/or @sourceFecPayloadID information.

Each element can be used to provide information as illustrated in thefigure.

According to an embodiment of the present invention, a broadcastreceiver or a broadcast transmitter can use @deliveryObjectFormatinformation (or field) of the PayloadFormat element in the SourceFlowelement of the LSID in order to identify a ROUTE packet including theinitialization segment.

In one embodiment, @deliveryObjectFormat information can indicate thatthe corresponding ROUTE packet includes a signaling message format whenthe value thereof is 0. When the @deliveryObjectFormat information has avalue of 0, the @deliveryObjectFormat information can indicate that aROUTE packet having the same code point (CP) in an LCT packet header asthe value of @codePoint information allocated to the PayloadFormatelement carries data in the aforementioned signaling message format. Theinitialization segment can be included in the signaling message formatand transmitted. Transmission of other signaling data such as servicesignaling data and component signaling data in the signaling messageformat through ROUTE packets using the same method as the one above canbe recognized through the @deliveryObjectFormat information.

When the @deliveryObjectFormat information has a value of 4, the@deliveryObjectFormat field can indicate that the corresponding ROUTEpacket includes metadata (signaling information) containing theinitialization segment. When the @deliveryObjectFormat field has a valueof 4, the @deliveryObjectFormat information can indicate transmission ofa metadata format including the initialization segment through a ROUTEpacket or direct transmission of the initialization segment through theROUTE packet.

According to an embodiment of the present invention, the broadcastsystem (broadcast receiver and/or broadcast transmitter) can signaldirect transmission of other signaling data such as service signaling(service level signaling information) and/or component signaling(component level signaling information) through ROUTE packets byallocating a new value (e.g. a value equal to or greater than 5) to the@deliveryObjectFormat information.

According to another embodiment of the present invention, the broadcastsystem may identify a ROUTE packet carrying signaling data such as theinitialization segment through other fields or new additional fields inthe LSID in addition to the method of using the @deliveryObjectFormatinformation described in the present embodiment.

FIG. 92 shows signaling object description (SOD) providing informationfor filtering a service signaling message according to an embodiment ofthe present invention.

The signaling object description according to an embodiment of thepresent invention can include @protocolVersion, @dataVersion,@validFrom, @expiration, Signaling Object element, @toi, @type,@version, @instance Id, @validFrom, @expiration and/or @payloadFormat.

The @protocolVersion information indicates the version of the signalingobject description.

The @dataVersion information indicates the version of instances of thesignaling object description. The @dataVersion information can bechanged when the contents of the signaling object description arevaried.

The @validfrom information indicates the time from when the instances ofthe signaling object description start are available. The receiver canrecognize the time from which the signaling object description isavailable using the @validfrom information and use information includedin the signaling object description from the corresponding time.

The @expiration information indicates the time at which availability ofthe instance of the signaling object description expires. The receivercan recognize the time at which availability of the signaling objectdescription expires and manage information of the signaling objectdescription using the @validfrom information.

The Signaling Object element indicates an object including signalinginformation. The signaling object description can include signalinginformation about one or more signaling objects.

The @toi information indicates a transmission object identifier (TOI)allocated to a signaling object. The @toi information can be used toidentify a packet associated with the signaling object. The receiver canidentify the following information including the type and/or version ofa signaling message transmitted through each object by mapping the @toiinformation to a TOI of an LCT packet.

The @type information identifies the type of a signaling messageincluded in an object. For example, the @type information can indicatetransmission of LSID (LCT Session Instance Description) as a signalingmessage in the corresponding object when the value thereof is 0,transmission of CMD (Component Mapping Description) as a signalingmessage in the corresponding object when the value thereof is 1,transmission of ASD (Application Signaling Description) as a signalingmessage in the corresponding object when the value thereof is 2,transmission of MPD (Media Presentation Description) as a signalingmessage in the corresponding object when the value thereof is 3,transmission of USD (URL Signaling Description) as a signaling messagein the corresponding object when the value thereof is 4, andtransmission of the IS (Initialization Segment) as a signaling messagein the corresponding object when the value there of is 5.

The @version information indicates the version of a signaling message.The receiver can recognize change of the signaling message throughvariation of the value of this field.

The @instance Id information identifies an instance of a signalingmessage. This information can be used for the receiver to identifyinstances of signaling messages, which can be present in one service,such as initialization segments.

The @validFrom information indicates the time from which a signalingmessage included in an object is available. The receiver can recognizethe time from which the signaling message included in the correspondingobject is available using this information and use the signaling messageincluded in the object from the corresponding time.

The @expiration information indicates the time for which the signalingmessage included in the object is valid. The receiver can recognize thetime at which availability of the signaling message included in theobject expires and manage the signaling message using this information.

The @payloadFormat information indicates the format of signaling messagedata included in the corresponding object. For example, a signalingmessage can be provided in a binary format or XML and the @payloadFormatinformation indicates this format.

When signaling messages are transmitted with an LCT based protocol suchas ROUTE, each signaling message can be set as an object and processed.Since an object can be identified by the unique TOI thereof in theaforementioned protocol, signaling messages can be filtered by mappingsignaling message related information such as version and type to eachTOI. The aforementioned SOD (Signaling Object Description) providesfiltering information of signaling objects corresponding to a singletransport session. The signaling object description can be transmittedthrough internal or external means of a signaling transport session.When the signaling object description is transmitted through theinternal means, the receiver can identify the signaling objectdescription with a unique TOI value (e.g. 0 or 0xFFFF) and interpret thesignaling object description prior to other signaling messagestransmitted along therewith. When the signaling object description istransmitted through the external means, the signaling object descriptionis transmitted through a fast information channel (FIC), a service listtable (SLT), a separate IP datagram or a different ROUTE session priorto other objects delivered in the corresponding session such that thereceiver can previously acquire information of the correspondingsignaling message.

FIG. 93 illustrates an object including a signaling message according toan embodiment of the present invention.

When signaling messages are transmitted using an LCT based protocol suchas ROUTE, each signaling message can be set as an object and processed.An object can be identified by the unique TOI thereof in theaforementioned protocol. The receiver can filter signaling messages bymapping signaling message related information such as version and typeto each TOI. Objects containing different content may be assigneddifferent TOIs. In this case, the broadcast system can process signalingmessages through a method compatible with a conventional objectprocessing method since all objects can be uniquely identified.

FIG. 93 illustrates an embodiment in which part of a TOI field is usedfor description of fixed-length signaling message related information.In the present embodiment, a 32-bit TOI field is used, and the type andversion of signaling data transmitted through the corresponding objectcan be identified through a 16-bit type field and a 16-bit versionfield. In the same manner, additional information of the aforementionedsequence number information, validfrom information, expirationinformation and/or payload format information may be delivered byallocating part of the TOI field to fixed-length fields.

The object according to an embodiment of the present invention caninclude V, C, PSI, S, O, H, A, B, HDR_LEN, Codepoint, Congestion ControlInformation, Transport Session Identifier (TSI), Transport ObjectIdentifier (TOI), Header Extensions, FEC payload ID and/or EncodingSymbols elements. Here, an element may be referred to as information ora field.

The PSI element can include an X element and/or a Y element.

The TOI element can include a Type element and/or a Version element.

The V element indicates the version number of a packet. The V elementcan indicate the version of ALC/LCT. The V element can indicate thatpackets conforming to ALC/LCT+ are transmitted through the correspondingobject.

The C element corresponds to a congestion control flag. The C elementindicates the length of a congestion control information (CCI) element.For example, the C element can indicate a CCI length of 32 bits when thevalue thereof is 0, a CCI length of 64 bits when the value thereof is 1,a CCI length of 96 bits when the value thereof is 2, and a CCI length of128 bits when the value thereof is 3.

The PSI element may correspond to protocol-specific indication (PSI).The PSI element can be used as an indicator of a specific purpose for anupper protocol of ALC/LCT+. The PSI element can indicate whether thecurrent packet corresponds to a source packet or an FEC repair packet.

The X element may correspond to information indicating a source packet.When different FEC payload ID formats are respectively used for sourcedata and repair data, the X element indicates the FEC payload ID formatfor the source data when the value thereof is 1 and indicates the FECpayload ID format for the repair data when the value thereof is 0. Whenthe X element is set to 0 in the transmitter, the receiver may ignorethis element or packet and may not process the same.

The S element may correspond to a transport session identifier flag. TheS element indicates the length of the transport session identifierelement

The O element may correspond to a transport object identifier flag. TheO element indicates the length of the transport object identifierelement. An object refers to one field and the aforementioned TOI isidentification information of each object. A file corresponding to a TOIof 0 can include signaling information associated therewith.

The H element may correspond to a half-word flag. The H elementindicates whether to add a half-word (16 bits) to the TSI and TOIfields.

The A element may correspond to a close session flag. The A elementindicates that a session is closed or closure of the session isimminent.

The B element may correspond to a close object flag. The B elementindicates that an object is closed or closure of the object is imminent.

The HDR_LEN element indicates the length of a header of a packet.

The Codepoint element indicates the type of a payload transmitted by thepacket. An additional payload header can be inserted into a prefix ofpayload data according to payload type.

The congestion control information (CCI) element may include congestioncontrol information such as layer numbers, logical channel numbers andsequence numbers. The CCI element may include necessary congestioncontrol related information.

The transport session identifier (TSI) element is a unique identifier ofa session. The TSI element indicates one of all sessions from a specificsender. The TSI element identifies a transport session. The value of theTSI element can be used for one track.

The transport object identifier (TOI) element is a unique identifier ofan object. The TOI element indicates an object to which thecorresponding packet belongs in a session. The value of the TOI elementcan be used for one piece of ISO BMFF object data. The TOI element caninclude the ID of an ISO BMFF file and the ID of a chunk. The TOIelement can have a combination of the ISO BMFF file ID and the chunk IDas a value thereof.

The Type element identifies the type of data transmitted through thecorresponding object. For example, the Type element can indicate thatthe data transmitted through the corresponding object is a signalingmessage.

The Version element identifies the version of the data transmittedthrough the corresponding object. For example, the Version element caninclude information indicating whether the structure and/or contents ofthe data identified through the Type object have been changed.

The Header Extensions element may include additional header information.

The FEC payload ID element is an FEC payload identifier. The FEC payloadID element includes identification information of a transmission blockor an encoding symbol. The FEC Payload ID indicates an identifier whenthe file has been FEC-encoded. For example, when the FLUTE protocol filehas been FEC encoded, the FEC Payload ID can be allocated by abroadcaster or a broadcast server to identify the same.

The Encoding Symbols element may include data of the transmission blockor encoding symbol.

FIG. 94 illustrates TOI configuration description (TCD) according to anembodiment of the present invention.

As described above, part of the TOI field can be used for description ofvariable-length signaling message related information. For descriptionof signaling message related information in the variable-length TOIfield, TOI field configuration information may be separatelytransmitted. In an embodiment, the TOI configuration description asshown in the table can be transmitted and/or received to provide TOIfield configuration information. In the present embodiment, the TCDprovides TOI field configuration information of transport packetscorresponding to one transport session. The TCD can be transmittedthrough internal means and/or external means of a signaling transportsession. When the TCD is transmitted through the internal means, the TCDcan be identified with a unique TOI value, e.g. 0 or 0xFFFF andinterpreted prior to other signaling messages transmitted alongtherewith. When the TCD is transmitted through the external means, theTCD is transmitted through an FIC, separate IP datagram or a differentROUTE session prior to objects delivered in the corresponding sessionsuch that the receiver can previously recognize TOI field configurationinformation included in each packet. @typeBits and following fieldsrespectively indicate the lengths of fields in TOI and represent thatfield information corresponding to the respective lengths is describedin the order of bits from the TOI start bit.

The TCD according to an embodiment of the present invention can include@protocolVersion, @dataVersion, @validFrom, @expiration, @typeBits,@versionBits, @instanceIdBits, @validFromBits, @expirationBits and/or@payloadFormatBits information.

The @protocolVersion identifies the version of the TCD. The@protocolVersion information indicates a variation in the protocol orstructure of the TCD if the variation is present.

The @dataVersion information identifies the version of an instance ofthe TCD. The @dataVersion indicates variation in the contents of the TCDif the contents of the TCD are changed.

The @validFrom information indicates the time from which instances ofthe TCD are available. The receiver can recognize the time from whichthe TCD is available using the @validFrom information and useinformation of the TCD from the corresponding time.

The @expiration information indicates the time at which availability ofthe instances of the TCD expires. The receiver can recognize the time atwhich availability of the TCD expires and terminate use of informationof the TCD using the @expiration information. The receiver can manageTCD information using the @expiration information.

The @typeBits information indicates the length of the type field in theTOI field. The @typeBits information can represent the length of thetype field in bits.

The @versionBits information indicates the length of the version fieldin the TOI field. The @versionBits information can represent the lengthof the version field in bits.

The @instanceIdBits information indicates the length of the instanceIDfield in the TOI field in bits.

The @validFromBits information indicates the length of the validFromfield in the TOI field in bits.

The @expirationBits information indicates the length of the expirationfield in the TOI field in bits.

The @payloadFormatBits information indicates the length of thepayloadFormat field in the TOI field in bits.

FIG. 95 illustrates a payload format element of a transport packetaccording to an embodiment of the present invention.

According to an embodiment of the present invention, a signaling messagecan be transmitted through a payload of a transport packet. To this end,the transport packet may include the payload format element shown in thefigure. The transport packet corresponds to a packet carrying objectsincluding broadcast data. The name of the transport packet according tothe present invention may depend on the protocol by which the packet isprocessed. For example, when the packet is processed through ROUTE, thepacket can be called a ROUTE packet.

The payload format element can be included in LSID as described above.

The payload format element of the transport packet according to thepresent invention can include @codePoint, @deliveryObjectFormat,@fragmentation, @deliveryOrder, @sourceFecPayloadID and/or TCID (TOIConfiguration Instance Description) information.

The @codePoint information defines what code point is used for thecorresponding payload. This information may play the same role as theaforementioned CP element or may have the same value as the CP element.

The @deliveryObjectFormat information specifies the payload format of anobject for data delivery. For example, this information can indicatethat the object carries a signaling message, a file, an entity, apackage or metadata including an initialization segment.

The @fragmentation information specifies the type of fragmentation.

The @deliveryOrder information specifies the order of delivery ofobjects. For example, this information can be used to specify the orderof objects transmitted through the current payload.

The @sourceFecPayloadID information defines the format of the Source FECPayload ID.

When part of the TCID is used for description of variable-lengthsignaling message related information, the TCID can include TOI fieldconfiguration information.

FIG. 96 illustrates TOI configuration instance description (TCID)according to an embodiment of the present invention.

Part of the TOI field is used for description of variable-lengthsignaling message related information and a TOI field configuration canbe dynamically changed in one transport session.

For description of signaling message related information in thevariable-length TOI field, TPO field configuration information can beseparately transmitted. Such TOI field configuration information may betransmitted in the illustrated format.

In the present embodiment, the TCID provides TOI field configurationinformation of transport packets corresponding to a group of packetsmapped to one code point value. The TCID can be included inPayloadFormat in SourceFlow of the LSID. Internal fields of the TCID maycorrespond to those of the aforementioned TCD and indicate a TOIconfiguration of packets having the same CP value as @codePoint includedalong with the TCID in PayloadFormat. A method of configuring the TOImay correspond to the aforementioned TCD configuration method.

The TCID according to an embodiment of the present invention can include@typeBits, @versionBits, @instanceIdBits, @validFromBits,@expirationBits and/or @payloadFormatBits information. For descriptionof such information, refer to description of the aforementionedinformation having the same names

FIG. 97 illustrates a syntax of a fast information channel (FIC) payloadaccording to an embodiment of the present invention.

While signaling data including information for service scan oracquisition is referred to as FIC in the present invention, the name ofthe signaling data is not limited thereto. A description will be givenof signaling data providing information for acquiring broadcast servicesmore effectively at a lower layer of the service layer (or level). Forexample, such signaling data can be called a service list table or aservice list element.

While the signaling data structure is shown in the form of a binarytable for convenience of description in the present invention, identicalor similar information belonging to the table may be implemented in XML.

FIC according to an embodiment of the present invention can includeFIC_protocol_version information, transport_stream_id information,num_partitions information, partition_id information,partition_protocol_version information, num_services information,service_id information, service_data_version information,service_channel_number information, service_category information,short_service_name_length information, short_service_name information,service_status information, service_distribution information,sp_indicator information, IP_version_flag information,SSC_source_IP_address_flag information, SSC_source_IP_addressinformation, SSC_destination_IP_address information,SSC_destination_UDP_port information, SSC_TSI information, SSC_DP_IDinformation, num_partition_level_descriptors information, apartition_level_descriptor( ) element, num_FIC_level_descriptorsinformation and/or an FIC_level_descriptor( ) element.

The FIC_protocol_version information specifies the version of thestructure of the FIC.

The transport_stream_id information specifies a broadcast stream. Thisinformation may correspond to information specifying a whole broadcaststream.

The num_partitions information indicates the number of partitions in abroadcast stream. A single broadcast stream can be divided into one ormore partitions and each partition can include one or more data pipesused by a single broadcaster (or broadcast source).

The partition_id information specifies a partition.

The partition_protocol_version information specifies the version of thestructure of a partition.

The num_services information indicates the number of broadcast servicesone or more components of which are transmitted through the partition.

The service_id information specifies a service (or broadcast service).

The service_data_version information specifies a variation in a serviceentry for a service signaled by the FIC when the variation is present.In addition, the service_data_version information specifies a variationin a signaling table for services, included in a service signalingchannel (or service level signaling) when the variation is present. Thevalue of the service_data_version information can be increased wheneverthe variation is present to indicate the variation.

The service_channel_number information indicates the channel number fora service.

The service_category information indicates the category of a service.For example, the service_category information can indicate that abroadcast service is an A/V service, an audio service, an ESG(Electronic Service Guide), an App based service and/or CoD (Content onDemand)

The short_service_name_length information indicates the length of theshort_service_name information. The short_service_name_length may have avalue of 0 when the short_service_name information is not present.

The short_service_name information indicates the short name of aservice. Each character indicated by the short_service_name informationcan be encoded per UTF-8. When there is an odd number of bytes in theshort name, the second byte of the last of the byte pair per pair countindicated by the short_service_name_length field can contain 0x00.

The service_status information indicates the status of a service. Theservice_status information can indicate that the broadcast service isactive, inactive, suspended, hidden and/or shown.

The service_distribution information specifies whether representation ofbroadcast services or broadcast content is possible only with thecurrent partition, the current partition is necessary for therepresentation although the representation is impossible only with thecurrent partition, other partitions are necessary for therepresentation, or other broadcast streams are necessary for therepresentation.

The sp_indicator information indicates application of serviceprotection. The sp_indicator information specifies whether one or morecomponents of a broadcast service, which are necessary for significantrepresentation, are protected.

The IP_version_flag information specifies whether the IP addressindicated by the SSC_source_IP_address information and/or theSSC_destination_IP_address is an IPv4 address or an IPv6 address.

The SSC_source_IP_address_flag information specifies presence of theSSC_source_IP_address information for services.

The SSC_source_IP_address information is present when the value of theSSC_source_IP_address_flag information is set to 1 and not present whenthe value of the SSC_source_IP_address_flag information is set to 0. TheSSC_source_IP_address information indicates the source IP address of anIP datagram (or data unit) carrying signaling information for a service.The SSC_source_IP_address information can be 128 bits when an IPv6address is used.

The SSC_destination_IP_address information indicates the destination IPaddress of the IP datagram (or data unit) carrying the signalinginformation for the service. The SSC_destination_IP_address informationcan be 128 bits when an IPv6 address s is used.

The SSC_destination_UDP_port information indicates the destination UDPport number for UDP/IP streams carrying the signaling information forthe service.

The SSC_TSI information indicates a transport session identifier (TSI)of an LCT channel through which signaling information (or signalingtable) for a service is transmitted.

The SSC_DP_ID information specifies a data pipe including signalinginformation (or a signaling table) for a service. The data pipe throughwhich the signaling information is transmitted may correspond to themost robust data pipe in the current partition or broadcast stream.

The num_partition_level_descriptors information indicates the number ofpartition level descriptors defined for partitions.

The partition_level_descriptor( ) element includes one or more partitionlevel descriptors. A partition level descriptor may include informationnecessary for the receiver to access, acquire or use partitions.

The num_FIC_level_descriptors information indicates the number of FIClevel descriptors defined for the FIC.

The FIC_level_descriptor( ) element includes one or more FIC leveldescriptors. An FIC level descriptor can include additional signalinginformation for the FIC.

FIG. 98 illustrates a syntax of a payload of the FIC according toanother embodiment of the present invention.

The payload of the FIC according to another embodiment of the presentinvention may additionally include SSC_delivery_type, SSC_URL_lengthand/or SSC_URL_data information in addition to the FIC payload in theaforementioned embodiment.

The SSC_delivery_type information specifies a path through whichsignaling information (e.g. service signaling channel or service levelsignaling) associated with a service is delivered. The SSC_delivery_typeinformation can specify whether service level signaling data istransmitted through a broadband network (Internet). For example, theSSC_delivery_type information can indicate that service level signalingis transmitted through a broadcast network when the value thereof is0x01. The SSC_delivery_type information can indicate that service levelsignaling is transmitted through the Internet when the value thereof is0x02.

The SSC_URL_length information indicates the length of the SSC_URL_datainformation.

The SSC_URL_data information indicates the URL of a service or locationproviding signaling information associated with a service.

For description of information which is not described in the presentembodiment, refer to the aforementioned corresponding description.

FIG. 99 illustrates a syntax of service level signaling according toanother embodiment of the present invention.

Information necessary for the receiver to receive a broadcast serviceand/or broadcast content that a viewer desires may be referred to asservice level signaling. The service level signaling includesinformation describing attributes of broadcast services and componentsincluded in broadcast services.

Service level signaling data according to another embodiment of thepresent invention may include a signaling message header and/or aservice signaling message.

The service level signaling data according to another embodiment of thepresent invention can include @service_id information, @service_categoryinformation, @service_name information, @channel_number information,@service_status information, @service_distribution information,@SP_indicator information, a ROUTE Session element, @sourceIPAddrinformation, @destIPAddr information, @destUDPPort information, @LSID_DPinformation, a Targeting element, a Content Advisory element, a RightIssuer Service element, a Current Program element, an Original ServiceIdentification element, a Content Labeling element, a Genre element, aCaption element and/or a Protection element.

The @service_id information specifies a broadcast service.

The @service_category information specifies the category of thebroadcast service. For example, the @ service_category information canspecify whether the broadcast service is an audio service, a real-timebroadcast service, a non-real time broadcast service, a linear broadcastservice, an app-based broadcast service or a service guide.

The @service_name information indicates the name of the broadcastservice.

The @channel_number information indicates the channel numbercorresponding to the channel through which the broadcast service istransmitted. This channel number may correspond to a logical/physicalchannel number. This channel number may be used as informationspecifying a logical path or a transport unit through which servicelevel signaling data is transmitted as necessary.

The @service_status information indicates the status of the broadcastservice. The @service_status information may include informationspecifying whether the broadcast service is active or inactive. The@service_status information may include information specifying whetherthe broadcast service is hidden.

The @service_distribution information indicates how data or componentsfor the broadcast service are distributed and transmitted.

The @SP_indicator information specifies whether service protection hasbeen applied to the broadcast service or at least one component includedin the broadcast service. The @SP_indicator information may correspondto information specifying whether service protection has been applied todata units or components for meaningful representation of the broadcastservice.

The ROUTE Session element includes information about a ROUTE sessionthrough which the broadcast service or components included in thebroadcast service are transmitted.

The @sourceIPAddr information indicates the source IP address of IPdatagrams (or data units) carrying a ROUTE packet.

The @destIPAddr information indicates the destination IP address of theIP datagrams (or data units) carrying the ROUTE packet.

The @destUDPPort information indicates the destination port number ofthe IP datagrams (or data units) carrying the ROUTE packet.

The @LSID_DP information specifies a data pipe through which information(e.g. LSID) that describes transport parameters associated with theROUTE session and/or lower sessions of the ROUTE session is delivered.

The Targeting element includes information for providing personalizedbroadcast services (targeted broadcast). This element can be included inservice level signaling as a separate signaling structure. In this case,this element can include link information about the service levelsignaling.

The Content Advisory element includes information about rating of thebroadcast service. This element can be included in service levelsignaling as a separate signaling structure. In this case, this elementcan include link information about the service level signaling. TheRight Issuer Service element includes information related to the rightto appropriately consume the broadcast service. This element can beincluded in service level signaling as a separate signaling structure.In this case, this element can include link information about theservice level signaling.

The Current Program element includes information about the currentbroadcast program. This element can be included in service levelsignaling as a separate signaling structure. In this case, this elementcan include link information about the service level signaling.

The Original Service Identification element includes information forspecifying the original service associated with the current broadcastservice. This element can be included in service level signaling as aseparate signaling structure. In this case, this element can includelink information about the service level signaling.

The Content Labeling element includes information about contentlabeling. This element can be included in service level signaling as aseparate signaling structure. In this case, this element can includelink information about the service level signaling. The Genre elementincludes information for classifying the genre of the broadcast service.This element can be included in service level signaling as a separatesignaling structure. In this case, this element can include linkinformation about the service level signaling.

The Caption element includes information about the closedcaption/subtitle of the broadcast service. This element can be includedin service level signaling as a separate signaling structure. In thiscase, this element can include link information about the service levelsignaling.

The Protection element includes information about protection for thebroadcast service. When the aforementioned @SP_indicator informationspecifies that protection has been applied to the broadcast service orbroadcast components, the Protection element can provide detailedinformation about the protection. This element can be included inservice level signaling as a separate signaling structure. In this case,this element can include link information about the service levelsignaling.

FIG. 100 illustrates component mapping description according to anotherembodiment of the present invention.

The component mapping description according to another embodiment of thepresent invention may further include @partitionID information inaddition to the information or elements included in the componentmapping description according to the aforementioned embodiment.

The @partitionID information specifies a partition indicating abroadcast station in a broadcast stream. The @partitionID informationcan be used as information that specifies the transmission source ofbroadcast components.

Description of other information or elements included in the componentmapping description is replaced with the aforementioned description ofinformation or elements in the same names

FIG. 101 illustrates a syntax of URL signaling description according toanother embodiment of the present invention.

As described above, signaling information that describes a broadcastservice can be transmitted through a broadband network as well as abroadcast network. When the signaling information that describes abroadcast service is transmitted through the broadband network, thereceiver can acquire the signaling information through the URL signalingdescription.

The URL signaling description according to another embodiment of thepresent invention can include @service_id, @smtURL, @mpdURL, @cmtURL,@astURL, @gatURL and/or @eatURL information.

The @service_id information specifies a service.

The @smtURL information indicates the URL of a server or locationproviding a service map table (SMT) when the SMT is transmitted throughthe broadband network.

The @mpdURL information indicates the URL of a server or locationproviding an MPD when the MPD is transmitted through the broadbandnetwork.

The @cmtURL information indicates the URL of a server or locationproviding a component mapping table (CMT) when the CMT is transmittedthrough the broadband network.

The @astURL information indicates the URL of a server or locationproviding an application signaling table (AST) when the AST istransmitted through the broadband network.

The @gatURL information indicates the URL of a server or locationproviding a guide access table (GAT) when the GAT is transmitted throughthe broadband network. The GAT corresponds to a signaling messageincluding information for bootstrapping of an electronic service guide(ESG). That is, the GAT can correspond to a signaling message includinginformation necessary for the receiver to access the ESG.

The @eatURL information indicates the URL of a server or locationproviding an emergency alert table (EAT) when the EAT is transmittedthrough the broadband network. The EAT corresponds to a signalingmessage including emergency alert related information and an emergencyalert message.

FIG. 102 illustrates a SourceFlow element according to anotherembodiment of the present invention.

Broadcast service data can be transmitted per object through a ROUTEsession. Objects can be individually recovered. A source protocol can bedefined to transmit objects within one session, and the SourceFlowelement including information related to source (object) delivery can bedefined in the source protocol.

The SourceFlow element according to another embodiment of the presentinvention can further include @location information in addition to theinformation/attributes/elements included in the aforementionedSourceFlow element.

The @location information indicates a location or a data unit carryingsource flow data. The @location information specifies a data pipe in abroadcast stream. The receiver can recognize that the source flow datais transmitted through the data pipe.

Description of other information/attributes/elements included in theSourceFlow element is replaced by description of the aforementionedSourceFlow element.

FIG. 103 illustrates a process of acquiring signaling informationthrough a broadcast network according to another embodiment of thepresent invention.

The receiver can access a location carrying data of a service signalingchannel associated with a desired broadcast service using informationthat specifies services included in an FIC.

The receiver acquires information about the source IP address,destination IP address and/or UDP port number of IP datagrams carryingthe data of the service signaling channel, in the FIC.

The receiver acquires information that specifies a data pipe includingthe data of the service signaling channel, in the FIC. The receiver canaccess the data pipe carrying the data of the service signaling channelthrough the acquired information.

The receiver can access an LCT session through which the data of theservice signaling channel is transmitted using information thatspecifies the LCT session, which is included in the FIC. The LCT sessionthrough which the data of the service signaling channel is transmittedmay be fixed to an LCT session having a specific TSI. In this case, thereceiver can access the LCT session having the specific TSI in order toacquire the data of the service signaling channel without additionalinformation. The receiver can access the corresponding location toacquire the data of the service signaling channel

The receiver may access an LCT session through which the aforementionedLSID is transmitted. In this case, the TSI of the LCT session may befixed, and the receiver can access the LCT session having the TSI toacquire the LSID. The receiver can acquire components included in thebroadcast service using information of the LSID.

FIG. 104 illustrates a process of acquiring signaling informationthrough a broadcast network and a broadband network according to anotherembodiment of the present invention.

The receiver can access a location carrying data of a service signalingchannel associated with a desired broadcast service using informationthat specifies services included in an FIC.

The receiver acquires information about the source IP address,destination IP address and/or UDP port number of IP datagrams carryingthe data of the service signaling channel, in the FIC.

The receiver acquires information that specifies a data pipe includingthe data of the service signaling channel, in the FIC. The receiver canaccess the data pipe carrying the data of the service signaling channelthrough the acquired information.

The receiver accesses the data of the service signaling channel toacquire the aforementioned URL signaling table or URL signalingdescription. The receiver can access a server or location providingservice level signaling using information included in the URL signalingtable to acquire the service level signaling through the broadbandnetwork.

FIG. 105 illustrates a process of acquiring signaling informationthrough a broadband network according to another embodiment of thepresent invention.

When information specifying the transport type of a service signalingchannel, included in an FIC, indicates that data of the servicesignaling channel is transmitted through the broadband network, thereceiver acquires URL information about a service or location providingthe data of the service signaling channel in the FIC. In this case, theURL information can indicate the URL of a single server or locationproviding the whole data of the service signaling channel or URLs ofservers or locations respectively providing signaling structures (SMT,MPD, CMT, etc.) that can be included in the service signaling channel.

The receiver accesses the server or location indicated by the URLinformation to acquire the data of the service signaling channel throughthe broadband network.

FIG. 106 illustrates a process of acquiring an electronic service guide(ESG) through a broadcast network according to another embodiment of thepresent invention.

The receiver can recognize that a broadcast service corresponds to anESG from information specifying the category of the service, which isincluded in an FIC, and acquire information specifying a data pipethrough which data of a service signaling channel with respect to thecorresponding service is transmitted.

The receiver can access the specified data pipe to acquire data of theESG, transmitted through the data pipe.

While the ESG is regarded as a broadcast service, the ESG can beefficiently acquired through the aforementioned process since thecomplicated signaling structure to access general broadcast servicesneed not be interpreted.

FIG. 107 illustrates a process of acquiring video segments and audiosegments of a broadcast service through a broadcast network according toanother embodiment of the present invention.

The receiver acquires data of a service signaling channel and obtains asignaling structure (e.g. CMT) including information that describescomponents of the broadcast service, which is included in the data ofthe service signaling channel.

The receiver acquires information specifying a data pipe through which avideo component of the broadcast service is transmitted in the signalingstructure and accesses the data pipe using the acquired information. Thereceiver acquires a signaling structure (e.g. LSID) that describes anLCT session in a ROUTE session through which the data pipe istransmitted.

The receiver accesses the LCT session through which the video componentof the broadcast service is transmitted to acquire the video componentfrom the signaling structure that describes the LCT session.

The receiver acquires information specifying a data pipe through whichan audio component of the broadcast service is transmitted and accessesthe data pipe using the acquired information. The receiver acquires asignaling structure (e.g. LSID) that describes an LCT session in a ROUTEsession through which the data pipe is transmitted.

The receiver accesses the LCT session through which the audio componentof the broadcast service is transmitted to acquire the audio componentfrom the signaling structure that describes the LCT session.

According to the present invention, it is possible to efficientlyacquire components included in the broadcast service through theaforementioned signaling structure even when the components aretransmitted through respective transport paths. In addition, thetransmitter can freely transmit components of broadcast services througha region having a margin and thus can efficiently transmit a largeramount of broadcast data.

FIG. 108 illustrates a process of acquiring video segments of abroadcast service through a broadcast network and acquiring audiosegments of the broadcast service through a broadband network accordingto another embodiment of the present invention.

The receiver acquires data of a service signaling channel and obtains asignaling structure (e.g. CMT) including information that describescomponents of the broadcast service, which is included in the data ofthe service signaling channel.

The receiver acquires information specifying a data pipe through which avideo component of the broadcast service is transmitted in the signalingstructure and accesses the data pipe using the acquired information. Thereceiver acquires a signaling structure (e.g. LSID) that describes anLCT session in a ROUTE session through which the data pipe istransmitted.

The receiver accesses the LCT session through which the video componentof the broadcast service is transmitted to acquire the video componentfrom the signaling structure that describes the LCT session.

The receiver recognizes that an audio component is transmitted throughthe broadband network from the signaling structure including theinformation that describes the components of the broadcast service andacquires the address of a server or location carrying the audiocomponent. Alternatively, the receiver acquires the address providingsegments of the audio component using MPD and obtains the segments ofthe audio component from the address.

According to the present invention, even when components belonging toone broadcast service are respectively transmitted through heterogeneousnetworks, it is possible to efficiently access the components of thebroadcast service through the aforementioned signaling structure.

FIG. 109 is a diagram showing the syntax of a payload of an FICaccording to another embodiment of the present invention.

An object of the FIC described in the present invention is to provideinformation necessary for a receiver to rapidly acquire a service (abroadcast service, a broadband service, etc.). Accordingly, the FICprovides bootstrapping information for accessing service level signaling(service layer signaling). The receiver may receive the FIC at a lowerlayer of a service layer and rapidly acquire service level signaling,which is signaling information of the service layer, using informationincluded in the FIC. The receiver may rapidly access the service usingdescription information of a service included in the service levelsignaling.

Meanwhile, in another embodiment of the present invention, the FIC mayprovide information on a service and components (e.g., video, audio,etc.) configuring the service. In this case, when the receiver receivesthe FIC, the receiver may immediately access and reproduce thecomponents of the service using information on the service included inthe FIC or the components of the service, without accessing servicelevel signaling. For example, an emergency alert service requiring rapidaccess, an electronic program guide (EPG) service, etc. may provideinformation necessary to acquire data configuring the service in theFIC. In this case, the receiver may omit a process of accessing theservice level signaling and immediately access the service using theFIC.

The payload of the FIC according to another embodiment of the presentinvention may include FIC_protocol_version information,transport_stream_id information, num_partitions information,partition_id information, partition_protocol_version information,num_services information, service_id information, service_data_versioninformation, service_channel_number information, service_categoryinformation, short_service_name_length information, short_service_nameinformation, service_status information, service_distributioninformation, sp_indicator information, IP_version_flag information,source_IP_address_flag information, bootstrap_mode information,source_IP_address information, destination_IP_address information,destination_UDP_port information, SSC_tsi information, SSC_dp_idinformation, num_component information, component_id information,component_tsi information, component_dp_id information,num_component_descriptor information, a component_level_descriptor( )element, num_partition_level_descriptors information, apartition_level_descriptor( ) element, num_FIC_level_descriptorsinformation and/or an FIC_level_descriptor element.

The bootstrap_mode information may indicate the bootstrap mode ofbroadcast service component data. For example, if the value of thebootstrap_mode information is 0x00, this may indicate that the field forthis information is reserved for future use. If the value of thebootstrap_mode information is 0x01 or 0x03 to 0x07, this may indicatethat a signaling system for a normal bootstrap mode (bootstrap isperformed using the corresponding information after receiving servicesignaling) is provided in the broadcast system. That is, the normalbootstrap mode may refer to a mode for providing a signaling system suchthat a receiver performs a process of accessing service level signalingusing information on an FIC and acquiring data and information necessaryfor a service using information included in the service level signaling.If the value of the bootstrap_mode information is 0x02, this mayindicate that a signaling system for a fast bootstrap mode (fastbootstrap is performed using only signaling information received in theFIC) is provided in a broadcast system. That is, the fast bootstrap moderefers to a mode for providing a signaling system such that a receiverimmediately acquires a service and components included in the serviceusing information included in the FIC.

The bootstrap_mode information may identify a bootstrap mode indicatinga signaling structure used to acquire one or more components included ina broadcast service. In one embodiment, the bootstrap_mode informationidentifies whether the bootstrap mode corresponds to a first bootstrapmode or a second bootstrap mode, the first bootstrap mode may correspondto a mode for identifying a transmission location of service levelsignaling (or first level signaling data) using information included inthe FIC (or second level signaling data), acquiring service levelsignaling at the location, and acquiring one or more components usinginformation included in the service level signaling, and the secondbootstrap mode may correspond to a mode for acquiring one or morecomponents using information included in the FIC.

If the bootstrap_mode information identifies that the bootstrap modecorresponds to the first bootstrap mode, the FIC may further includeservice identification information for uniquely identifying a broadcastservice, num_component information indicating the number of componentsincluded in the broadcast service identified by the serviceidentification information, component identification information foruniquely identifying a component included in the broadcast service,component transport session identification information for identifying atransport session for transmitting packets including data of thecomponent identified by the component identification information,component data pipe identification information for identifying a datapipe of a physical layer for transmitting packets including the data ofthe component and/or a transport parameter descriptor including atransport protocol parameter of the packets including the data of thecomponent. The transport parameter descriptor will be described below.

The num_component information may indicate the number of componentsincluded in the service.

The component_id information identifies a component. The component_idinformation may correspond to an identifier for uniquely identifying thecomponent.

The component_tsi information identifies a transport session fortransmitting a packet including the data of the component. Thecomponent_tsi information may indicate a packet id (identifier)indicating the flow of the corresponding packet.

The component_dp_id information identifies a data pipe of a physicallayer for transmitting a packet including the data of the component.

The num_component_descriptor information indicates the number ofcomponent level descriptors for providing information on the component.

The Component_level_descriptor ( ) element may include a component leveldescriptor including information related to the component.

A description of the other information and/or elements included in theFIC is replaced by the above description of the information and/orelements having the same or similar names as in this specification.

FIG. 110 is a diagram showing the syntax of a payload of an FICaccording to another embodiment of the present invention.

One broadcast service may be transmitted through one or more ROUTEsessions. In this case, for fast bootstrap, several pieces ofinformation and/or elements may be included in the FIC. The receiver mayaccess ROUTE sessions for transmitting data included in a broadcastservice using only information included in the FIC and acquire data forthe broadcast service.

The FIC according to another embodiment of the present invention mayinclude FIC_protocol_version information, transport_stream_idinformation, num_partitions information, partition_id information,partition_protocol_version information, num_services information,service_id information, service_data_version information,service_channel_number information, service_category information,short_service_name_length information, short_service_name information,service_status information, service_distribution information,sp_indicator information, IP_version_flag information, num_ROUTE_sessioninformation, source_IP_address_flag information, ssc_flag information,bootstrap_mode information, source_IP_address information,destination_IP_address information, destination_UDP_port information,SSC_tsi information, SSC_dp_id information, num_component information,component_id information, component_tsi information, component_dp_idinformation, num_component_descriptor information, acomponent_level_descriptor( ) element, num_partition_level_descriptorsinformation, a partition_level_descriptor( ) element,num_FIC_level_descriptors information, and an FIC_level_descriptorelement.

The num_ROUTE_session information may include the number of ROUTEsessions for transmitting data for the broadcast service.

The ssc_flag information may indicate that a service signaling channelfor transmitting service signaling is present in the ROUTE session. Thessc_flag information may indicate whether service signaling istransmitted in the ROUTE session. Here, the service signaling channelmay correspond to service level signaling. If the service signaling istransmitted, information on a session for transmitting the servicesignaling and an identifier of a data pipe may be included.

A description of the other information and/or elements included in theFIC is replaced by the above description of the information and/orelements having the same or similar names as in this specification.

FIG. 111 is a diagram showing a transport_parameter_descriptor accordingto an embodiment of the present invention.

If data of each component is delivered through a transport protocol,when a transport protocol parameter for a transport packet including thedata of the component is signaled, the receiver may efficiently processthe transport packet including the data of each component usinginformation included in the corresponding signaling.

In one embodiment of the present invention, the shown descriptor isproposed in order to signal a transport protocol related parameter. Theshown descriptor may be represented in a bitstream or XML format.

The descriptor proposed in the present invention may be used as adescriptor of a component level, a partition level or an FIC level inthe above-described FIC. Alternatively, the descriptor proposed in thepresent invention may be delivered to the receiver through signaling ofa link layer which is a higher layer of a physical layer. Alternatively,the descriptor proposed in the present invention may be used as adescriptor of a component level and/or a service level in servicesignaling (service level signaling).

The transport_parameter_descriptor according to an embodiment of thepresent invention may include descriptor_tag information,descriptor_length information, codepoint_flag information,delivery_object_format_flag information, fragmentation_flag information,delivery_order_flag information, payload_id_scheme_flag information,code_point information, delivery_object_format information,fragmentation_scheme information, delivery_order information, and/orpayload_id_scheme information.

The descriptor_tag information may indicate that the descriptor deliversthe parameter of the transport protocol.

The descriptor_length information may indicate the length of thedescriptor.

The codepoint_flag information may correspond to a flag indicatingwhether codepoint information is present in the descriptor. Thecodepoint information may be present if the value of the codepoint_flaginformation is “true” and may not be present if the value of thecodepoint_flag information is “false”.

The delivery_object_format_flag information may correspond to a flagindicating whether delivery_object_format information is present in thedescriptor. The delivery_object_format information may be present if thevalue of the delivery_object_format_flag information is “true” and maynot be present if the value of the delivery_object_format_flaginformation is “false”.

The fragmentation_flag information may correspond to a flag indicatingwhether fragmentation_scheme information is present in the descriptor.The fragmentation_scheme information may be present if the value of thefragmentation_flag information is “true” and may not be present if thevalue of the fragmentation_flag information is “false”.

The delivery_order_flag information may correspond to a flag indicatingwhether delivery_order information is present in the descriptor. Thedelivery_order information may be present if the value of thedelivery_order_flag information is “true” and may not be present if thevalue of the delivery_order_flag information is “false”.

The payload_id_scheme_flag information may correspond to a flagindicating whether payload_id_scheme information is present in thedescriptor. The payload_id_scheme may be present if the value of thepayload_id_scheme_flag information is “true” and may not be present ifthe value of the payload_id_scheme_flag information is “false”.

The code_point information may indicate a parameter associated with atransport packet payload according to a codepoint value (e.g., acodepoint of an LCT packet header, etc.) if the codepoint value isincluded in a transport packet header. For example, a combination of thefollowing delivery_object_format information, fragmentation_schemeinformation, delivery_order information and/or payload_id_schemeinformation may be indicated.

The delivery_object_format information may indicate the format of adelivery object included in the payload of the transport packet. In oneembodiment, if the value of the delivery_object_format information is“0x00” and “0x05” to “0xff”, this may indicate that thedelivery_object_format information is reserved for future use. If thevalue of the delivery_object_format information is “0x01”, this mayindicate that the format of the delivery object is a file. If the valueof the delivery_object_format information is “0x02”, this may indicatethat the format of the delivery object is an entity mode. The entitymode includes a header and payload of an entity. If the value of thedelivery_object_format information is “0x03”, this may indicate that theformat of the delivery object is a package. The package is a combinationof two or more files. If the value of the delivery_object_formatinformation is “0x04”, this may indicate that the delivery objectincludes metadata.

The fragmentation_scheme information may indicate a fragmentation schemeused when one delivery object is fragmented and transmitted in one ormore transport packets. The fragmentation_scheme information indicates ascheme for fragmenting data transmitted in the delivery object if one ormore transport packets are transmitted in one delivery object. In oneembodiment, if the value of the fragmentation_scheme information is“0x00”, the fragmentation_scheme information may indicate that thefragmentation scheme is arbitrary. That is, if the fragmentation_schemeinformation is “0x00”, the fragmentation_scheme information may indicatethat fragmentation is performed without predetermined scheme. If thefragmentation_scheme information is “0x01”, the fragmentation_schemeinformation may indicate that one or more boxes of the ISOBMFF arefragmented such that the delivery object is included. If thefragmentation_scheme information is “0x02”, the fragmentation_schemeinformation may indicate that data based on the sample of the ISOBMFF isfragmented such that the delivery object is included.

The delivery_order information indicates the delivery order of eachtransport packet if data included in one delivery object is fragmentedand delivered in one or more transport packets. In one embodiment, ifthe value of the delivery_order information is “0x00”, thedelivery_order information may indicate that the delivery order isarbitrary. If the value of the delivery_order information is “0x01”, thedelivery_order information may indicate that the transport packets aretransmitted in configuration order of the ISOBMFF (in-order delivery).If the value of the delivery_order information is “0x02”, thedelivery_order information may indicate that the data is transmitted inthe transport packets in order of the media samples of the ISOBMFF andthe data is transmitted prior to the movie fragment in the ISOBMFF.

The payload_id_scheme information may indicate a scheme for allocating apayload id if a payload ID value is included in the transport packetheader. In one embodiment, if the value of the payload_id_schemeinformation is “0x00”, the payload_id_scheme information may indicatethat an FEC payload ID is not present and all delivery objects areincluded in the packet. If the value of the payload_id_schemeinformation is “0x01”, the payload_id_scheme information may indicatethat an FEC payload ID is defined by 32 bits and a start offset isrepresented in this object. If the value of the payload_id_schemeinformation is “0x02” to “0xff”, this may indicate that thepayload_id_scheme information is reserved for future use.

According to the embodiment of the present invention, signalinginformation such as a transport_parameter_descriptor may be transmittedat a lower layer (e.g., a physical layer, a link layer and/or a networklayer) of a layer for transmitting service level signaling, such that areceiver preferentially accesses a specific service before acquiring theservice level signaling.

FIG. 112 is a diagram showing a signaling structure in a process ofacquiring a broadcast service at a receiver according to anotherembodiment of the present invention.

Referring to the figure, the receiver may acquire signaling informationand/or video/audio data through the following steps.

Information on the bootstrap of service level signaling (servicesignaling) may be included in the FIC. The receiver may recognize thedata pipe of the physical layer for transmitting service level signalingusing the information included in the FIC.

The receiver may access the recognized data pipe to acquire servicelevel signaling.

The receiver may recognize the data pipe for transmitting an LSID forproviding information on one or more ROUTE sessions and/or informationassociated with each ROUTE session.

The receiver may acquire information on packets transmitted through theLCT session in the ROUTE session through the LSID and/or service levelsignaling.

The receiver may acquire and parse an MPD to acquire URL relatedinformation of a segment associated with video/audio.

The receiver may compare the URL related information of the segmentassociated with video/audio with a segment_URL_pattern of service levelsignaling to recognize a distribution path of the segment.

If the segment associated with video/audio is transmitted through abroadcast network, the receiver may compare the segment URL informationwith a file template in the LSID to recognize a transport session andjoin the transmission session, thereby acquiring the segment.

The receiver may reproduce video/audio using the acquired segment.

FIG. 113 is a flowchart illustrating a process of transmitting andprocessing a broadcast signal according to an embodiment of the presentinvention.

An apparatus for transmitting and processing a broadcast signalgenerates one or more first layer data units including first levelsignaling data and broadcast data for a broadcast service (JS126010).

The apparatus for transmitting and processing the broadcast signalgenerates one or more second layer data units including the one or morefirst layer data units and second level signaling data (JS126020).

The apparatus for transmitting and processing the broadcast signalgenerates a broadcast signal including the one or more second layer dataunits (JS12630).

FIG. 114 is a diagram showing an apparatus for processing a broadcastsignal according to an embodiment of the present invention.

The broadcast signal processing apparatus J126100 according to theembodiment of the present invention may include a protocol processorJ126200, a broadcast signal generator J126300 and a transmission unitJ126400.

The protocol processor J126200 includes a first level signaling encoderJ126210, a first layer encoder J126220, a second level signaling encoderJ126230 and/or a second layer encoder J126240.

The protocol processor J126200 processes broadcast data or signalingdata according to the protocol of the broadcast system.

The broadcast signal generator J126300 performs a series of processes oftransmitting the data processed by the protocol processor. The broadcastsignal generator J126300 may correspond to the above-described broadcastsignal encoder/processor of the physical layer.

The transmission unit J126400 transmits the broadcast signal.

The first level signaling encoder J126210 generates first levelsignaling data. The first level signaling data may correspond tosignaling information of a higher layer for providing informationdescribing the broadcast service.

The first layer encoder J126220 generates broadcast data according tothe protocol of the first layer. The protocol of the first layer maycorrespond to a protocol according to MPEG-DASH, NRT and MMT.

The second level signaling encoder J126230 generates second levelsignaling data. The second level signaling data may include informationfor obtaining information on the first level signaling data at a lowerlayer of a layer for processing the first level signaling data. Thesecond level signaling data may include information necessary to scanthe broadcast service at the lower layer of the layer for processing thefirst level signaling data to rapidly generate a map for the broadcastservice.

The second layer encoder J126240 processes the data processed at thefirst layer according to the protocol of the second layer. The protocolof the second layer may correspond to an MMTP (MPEG Media TransportProtocol), ROUTE (ALC/LCT) and/or HTTP protocol.

According to the present invention, it is possible to rapidly acquiresignaling information provided at each layer after physical layerprocessing.

According to the present invention, signaling information of a higherlayer and/or processing broadcast data at each layer may be provided assignaling information, such that a receiver rapidly acquires andprocesses a broadcast service.

FIG. 115 is a diagram showing some of fast information channel (FIC)data according to another embodiment of the present invention.

FIG. 116 is a diagram showing the other of the FIC data according toanother embodiment of the present invention.

In these figures, one table is shown in a state of being divided intotwo tables, due to spatial restriction.

The shown FIC data may further include a field indicating the type of aprotocol for delivering service signaling information and a fieldindicating information on a path for delivering the service signalinginformation according to protocol. Here, the service signalinginformation may correspond to the above-described SLS. Here, the FICdata may correspond to the above-described SLT. Although the shown FICdata is represented in a bitstream format, the FIC data may berepresented in another format such as XML.

The fields included in the FIC data according to the shown embodimentwill be described. Fields having the same names may be equal to theabove-described fields.

The FIC_protocol_version field may indicate the version of the FIC dataor the protocol version of the FIC data. That is, this field mayindicate the version or protocol version of the SLT.

The transport_stream_id field may be the identifier of the fullbroadcast stream. This field may be equal to the above-described bsidfield. The broadcast stream may be unique in a specific area (e.g.,North America).

The num_partitions field may indicate the number of partitions presentin the broadcast stream. Here, the broadcast stream may mean a broadcaststream identified by the above-described transport_stream_id field.Here, assume that one broadcast stream may be divided into one or morepartitions. Each partition may include a plurality of PLPs. Eachpartition may be used by one service provider (broadcaster). That is,each partition may mean a portion of a broadcast stream used by oneservice provider.

Information/fields of partitions corresponding in number to the numberindicated by the above-described num_partitions field may be listed. Thebelow-described fields may be information described with respect to onepartition and more fields may be further included according to thenumber of partitions.

The partition_id field may be an identifier for identifying thepartition. This field may correspond to the above-described @providerId.That is, this field may be used to identify each service provider. Insome embodiments, the @providerId field may be included in the LLStable, instead of the SLT. The LLS table may include the SLT.

The partition_protocol_version field may indicate the version of thepartition or the protocol version of the partition.

The transport_protocol_type field may indicate the type of the protocolfor delivering components configuring one or more services provided bythe broadcaster or service signaling information of the services. Thatis, if the service components provided by the broadcaster or the servicesignaling information is delivered through the protocol such as ROUTE orMMTP, which protocol is used may be indicated. This field may correspondto the above-described @slsProtocolType. In some embodiments, if thisfield is 0x01, this may indicate MMT and, if this field is 0x02, thismay indicate a ROUTE protocol.

The num_services field may indicate the number of services included anddelivered in the partition. In some embodiments, this field may indicatethe number of services described in the SLT or FIC data. In anotherembodiment, this field may indicate the number of all services includedand delivered in the broadcast stream.

Information/fields of the services corresponding in number to the numberindicated by the above-described num_services field may be listed. Thefollowing fields may be information described with respect to onepartition and more fields may be further included according to thenumber of services.

The service_id field may mean the service identifier of each service.The service_data_version field may indicate the version of the serviceor the protocol version of the service.

The service_channel_number field may indicate the channel number of theservice. In some embodiments, this field may be divided into a fieldindicating the major channel number of the service and a fieldindicating the minor channel number. This field may correspond to theabove-described @majorChannelNo and @minorChannelNo.

The service_category field may indicate the category of the service.This may correspond to the above-described @serviceCategory. Forexample, a category such as an A/V service, an audio-only service, anESG service or an EA (Emergency Alert) service may be indicated by thisfield.

The short_service_name_length field may indicate the length of thebelow-described short_service_name field. The short_service_name fieldhaving the length indicated by this field may follow.

The short_service_name field may indicate the name or simplified name ofthe service. This field may correspond to the above-described@shortServiceName field.

The service_status field may indicate the status of the service. Forexample, the status of the service may be classified intoactive/suspended or hidden/shown.

The service_distribution field may indicate how the service isdistributed. This field may indicate whether the service is deliveredthrough only this partition, whether the service is not deliveredthrough only this partition but is reproducible through only thispartition, whether data of another partition is necessary forreproduction, whether data of another broadcast stream is necessary forreproduction, etc.

The sp_indicator field may be a flag indicating whether the service isin a production state. This field may indicate whether at least oneservice component included in the service is in a production state.Here, at least one service component may mean service componentsnecessary to meaningfully reproduce the service. This field maycorrespond to the above-described @protected.

The IP_version_flag field is a flag and may indicate that asource_IP_address and a destination_IP_address field are IPv4 addressesif the value of this field is 0. If the value of this field is 1, thismay indicate that the source_IP_address and the destination_IP_addressfield are IPv6 addresses. In some embodiments, this field may bereserved for future use.

The num_session field may indicate the number of transport sessions fordelivering the service. Here, the transport session may mean theabove-described ROUTE session or MMTP session. In some embodiments, thisfield may indicate the number of transport sessions for delivering theservice signaling information of the service. In this embodiment, thenumber of transport sessions for delivering the service signalinginformation may be one and thus the num_session field may be omitted.

Information/fields of the sessions corresponding in number to the numberindicated by the above-described num_session field may be listed. Thebelow-described fields are information described with respect to onesession and more fields may be further included according to the numberof sessions.

The source_IP_address_flag field may be a flag indicating whether thebelow-described source_IP_address field is present.

The ssc_flag field may be a flag indicating whether the below-describedSSC_tsi field and SSC_dp_id field are present.

The source_IP_address field may indicate source IP address informationof the transport session for delivering the service signalinginformation of the service. Here, the transport session may mean theabove-described ROUTE or MMTP session. This field may correspond to theabove-described @slsSourceIpAddress field. Presence of this field may bedetermined according to the value of the above-describedsource_IP_address_flag field. In some embodiments, this field mayindicate the source IP address information of the transport session fordelivering the service data of the service.

The destination_IP_address field may indicate destination IP addressinformation of the transport session for delivering the servicesignaling information of the service. This field may correspond to theabove-described @slsDestinationIpAddress field. In some embodiments,this field may indicate the destination IP address information of thetransport session for delivering the service data of the service.

The destination_UDP_port field may indicate destination UDP portinformation of the transport session for delivering the servicesignaling information of the service. This field may correspond to theabove-described @slsDestinationUdpPort field. In some embodiments, thisfield may indicate the destination UDP port information of the transportsession for delivering the service data of the service.

If the value of the above-described transport_protocol_type field is0x01, that is, if the service components or the signaling information ofthe service is transmitted according to MMTP, a packet_id field and adp_id field may be further added.

The packet_id field may have packet identifier information foridentifying a packet flow for delivering the service components of theservice or the service signaling information. Packets included in theMMTP packet flow may have packet identifiers indicated by this field.Through this information, the packet flow having the service signalinginformation may be identified in the MMTP transport session.

Although the packet flow for delivering the service signalinginformation is identified through the packet_id field in the presentembodiment, this field may be omitted according to embodiments.According to embodiments, the service signaling information of theservice may be delivered through a dedicated channel of the transportsession. For example, a packet flow having a packet ID having a value of00 may always deliver service signaling information in the transportsession. That is, in this case, when an MMTP session is identified usingIP and UDP information as bootstrap information, a packet flowidentified by the packet ID having the value of 00 in the MMTP sessionmay be accessed to acquire the service signaling information of theservice. Here, the predefined packet ID may have a value other than 00.

The dp_id field may be an identifier for identifying a physical channelfor delivering the service signaling information of the service, thatis, a PLP.

If the value of the above-described transport_protocol_type field is0x02, that is, if the components or the service signaling information ofthe service is transmitted according to the ROUTE protocol, an SSC_tsifield and an SSC_dp_id field may be further added. Presence of thesefields may be determined according to the value of the ssc_flag field.In addition, in some embodiments, an LSID_tsi field and a dp_id fieldmay be further added.

The SSC_tsi field may be session identifier information for identifyingan LCT transport session for delivering the service signalinginformation of the service. Through this information, an LCT sessionhaving service signaling information may be identified in the ROUTEtransport session.

Although the LCT session for delivering the service signalinginformation is identified through the SSC_tsi field in the presentembodiment, this field may be omitted according to embodiments. Inembodiments, the service signaling information of the service may bedelivered through the dedicated channel of the transport session. Forexample, an LCT session having a tsi value of 0 may always deliverservice signaling information in the transport session. That is, in thiscase, when the ROUTE session is identified using IP and UDP informationas bootstrap information, an LCT session identified by the tsi value of0 in the ROUTE session may be accessed to acquire the service signalinginformation of the service. Here, the predefined tsi value may have avalue other than 0.

The SSC_dp_id field may be an identifier for identifying the physicalchannel for delivering the service signaling information of the service,that is, a PLP.

The LSID_tsi field may be session identifier information for identifyingthe LCT session for delivering the above-described LSID. The dp_id fieldmay be PLP identifier information for identifying the physical channelfor delivering the LSID. Here, the LSID may correspond to theabove-described S-TSID. As described above, since the S-TSID is includedin the service signaling information, these fields may be equal to theabove-described SSC_tsi field and SSC_dp_id field and thus may beomitted. In an embodiment in which the LSID is transmitted independentlyof the service signaling information, these two fields (LSID_tsi fieldand dp_id field) may be necessary.

FIG. 117 is a diagram showing some of fast information channel (FIC)data according to another embodiment of the present invention.

FIG. 118 is a diagram showing the other of the FIC data according toanother embodiment of the present invention.

In these figures, one table is shown in a state of being divided intotwo tables, due to spatial restriction.

The FIC data of the shown embodiment is similar to the above-describedFIC data but may further include additional information/fields. Fieldshaving the same names as the fields of the above-described FIC data mayhave the same meanings.

In the present embodiment, a bootstrap_mode field is added to eachpartition. This field may indicate the bootstrap mode of the componentdata of services included in the partition. For example, if this fieldhas a value of 0x01, this may indicate that a normal bootstrap mode isused. If this field has a value of 0x02, this may indicate that a fastbootstrap mode is used. The other values may be reserved for future use.This field and the added fields may be omitted in a system which doesnot support the fast bootstrap mode cannot identify the bootstrap mode.

Here, the normal bootstrap mode is the above-described bootstrap mode inwhich an SLS is obtained using an SLT and service components of eachservice are accessed using the SLS.

Here, the fast bootstrap mode may mean that service components of eachservice are rapidly accessed using only information included in the SLT.

If the value of the bootstrap_mode field is 0x02, that is, in the caseof the fast bootstrap mode, FIC data may have access information foracquiring the components of each service. The role of the servicesignaling information in the above-described embodiment may be regardedas being performed by FIC data.

In this case, a num_component field may be added to each service. Thisfield may indicate the number of components of the service. Informationon the components corresponding in number to the number of componentsindicated by the num_component field may follow.

The component_id field may indicate the identifier of the component.This identifier may be equal to an identifier for identifying DASHrepresentation of an MPD or an asset ID of an MMT.

If the components of the service are transmitted according to the MMTprotocol, a component_packet_id field may be further added. This fieldmay indicate packet ID information of a packet flow for delivering thecomponent. The MMTP packets of this packet flow may have this packet ID.

If the components of the service are transmitted according to the ROUTEprotocol, a component_tsi field may be further added. This field mayindicate an identifier of a subsession of a transport session fordelivering the component. This subsession may mean an LCT session.

The component_dp_id field may identify a physical channel fortransmitting packets (ROUTE/LCT packets or MMTP packets) for deliveringthe component. That is, this field may include ID information of thePLP.

The num_component_descriptor field may indicate the number of componentlevel descriptors and component_level_descriptor( ) corresponding innumber to the number indicated by this field may be present. Thecomponent level descriptor may include information related to thecomponent.

Thereafter, the num_partition_level_descriptors field may be located toindicate the number of partition level descriptors.Partition_level_descriptor( ) corresponding in number to the numberindicated by this field may be present. The partition level descriptormay include information related to the partition.

Thereafter, a num_FIC_level_descriptors field may be located to indicatethe number of FIC level descriptors, and FIC_level_descriptor( )corresponding in number to the number indicated by this field may bepresent. The FIC level descriptor may include information related to theFIC.

Although omitted in the above-described embodiment, the partition leveldescriptor and the FIC level descriptor may be added regardless ofwhether the bootstrap mode is supported, in other embodiments of the FICdata.

FIG. 119 is a diagram showing some of fast information channel (FIC)data according to another embodiment of the present invention.

FIG. 120 is a diagram showing the other of the FIC data according toanother embodiment of the present invention.

In these figures, one table is shown in a state of being divided intotwo tables, due to spatial restriction.

The FIC data of the shown embodiment is similar to the above-describedFIC data, but the location of the above-describedtransport_protocol_type field is changed. Fields having the same namesas the fields of the above-described FIC data may have the samemeanings.

In the above-described embodiment, the transport_protocol_type field islocated at a partition level. In this case, the transport_protocol_typefield indicates the transport protocol of all services included in thepartition. One partition may refer to all data delivered by onebroadcaster. In this case, when services included in one partition usedifferent transport protocols, it is difficult to represent theservices.

In the present embodiment, the transport_protocol_type field may belocated at a service level. Therefore, a service provider using thispartition may easily specify a transport protocol with respect to eachservice. In addition, the service provider may use various transportprotocols, that is, use a ROUTE protocol with respect to a specificservice and use MMT protocol with respect to another service, therebyensuring system flexibility.

FIG. 121 is a diagram illustrating a method of processing service dataaccording to an embodiment of the present invention.

The method of processing service data according to the embodiment of thepresent invention may include generating service data and servicesignaling information, generating a service list table includingbootstrap information, processing the service data, etc. into broadcaststream and/or transmitting the broadcast stream.

First, the service data of the broadcast service and the servicesignaling information for signaling the service data may be generated(t507010). This step may be performed by a first module of atransmission side. The first module may correspond to a module forgenerating service data, etc. at a higher layer. Here, the servicesignaling information may include access information for acquiring theservice data. Here, the service data may mean actual service data suchas a service component included in the service and the service signalinginformation may correspond to the above-described SLS.

Thereafter, the service list table including the bootstrap informationfor locating the service signaling information may be generated(t507020). This step may also be performed by the first module of thetransmission side. Here, the service list table may correspond to theabove-described SLT. The bootstrap information may mean bootstrapinformation such as the above-described IP/UDP information.

The service data, the service signaling information and the service listtable may be processed into the broadcast stream (t507030). This stepmay be performed by a second module of the transmission side. The secondmodule may correspond to a module for managing a physical layer or alink layer. This step may correspond to the above-described process ofthe physical layer or the process of the physical layer and the linklayer.

Thereafter, the generated broadcast stream may be transmitted (t507040).This step may be performed by a third module of the transmission side.The third module may mean a transmission system such as an antenna.

In the method of processing the service data according to anotherembodiment of the present invention, the service data and the servicesignaling information may be delivered according to a first transportprotocol or a second transport protocol. Here, the first and secondtransport protocols may mean ROUTE and MMT protocols.

In the method of processing the service data according to anotherembodiment of the present invention, the service list table may furtherinclude service signaling protocol information, and the servicesignaling protocol information may indicate a type of a transportprotocol used to deliver the service signaling information. Here, theservice signaling protocol information may correspond to a fieldindicating the transport protocol for delivering the above-describedSLS.

In the method of processing the service data according to anotherembodiment of the present invention, the bootstrap information mayinclude Internet protocol (IP) information and user datagram protocol(UDP) information of a transport session for transmitting the servicesignaling information. Here, the IP information and the UDP informationmay mean the above-described destination IP address and the destinationUDP port number. This information may be used to identify a ROUTE orMMTP session for delivering an SLS.

In the method of processing the service data according to anotherembodiment of the present invention, if the service signalinginformation is delivered according to the first transport protocol, theservice signaling information may be delivered through a dedicatedsubsession of the transport session, and the dedicated subsession may beidentified by a predetermined session identifier value. Here, thetransport session may correspond to a ROUTE session and the subsessionmay correspond to an LCT session. The dedicated subsession may mean anLCT session for delivering an SLS identified by tsi=0. Here, thepredetermined session identifier value may mean tsi having a value of 0.In some embodiments, this value may not be 0.

In the method of processing the service data according to anotherembodiment of the present invention, if the service signalinginformation is delivered according to the second transport protocol, theservice signaling information may be delivered by second transportprotocol packets identified by a predetermined packet identifier value.Here, the second transport protocol packets may mean MMTP packets. Thepresent embodiment may correspond to the case where the SLS is deliveredby the packet flow identified by packet ID=00. The predetermined packetidentifier value may mean a packet ID having a value of 00. In someembodiments, this value may not be 0.

In the method of processing the service data according to anotherembodiment of the present invention, if the service signalinginformation is delivered according to the first transport protocol, theservice signaling information may be delivered through one subsession ofthe transport session, and the bootstrap information may further includesession identifier information of the subsession for delivering theservice signaling information. Here, the transport session maycorrespond to a ROUTE session and the subsession may correspond to anLCT session. The session identifier may mean tsi information.

In the method of processing the service data according to anotherembodiment of the present invention, if the service signalinginformation is delivered according to the second transport protocol, theservice signaling information may be delivered through one packet flowof the transport session, and the bootstrap information may furtherinclude packet identifier information for identifying packets of apacket flow for delivering the service signaling information. Here, thetransport session may correspond to an MMTP session and the packet flowmay correspond to an MMTP packet flow. The packet identifier informationmay mean the above-described packet ID.

In the method of processing the service data according to anotherembodiment of the present invention, the bootstrap information mayfurther include identifier information of a physical channel fortransmitting the service signaling information. Here, the physicalchannel may mean the above-described PLP or DP. The bootstrapinformation may further include PLP ID information for delivering theSLS as described above.

In the method of processing the service data according to anotherembodiment of the present invention, the processing of the service data,the service signaling information and the service list table into thebroadcast stream may include encapsulating the service data, the servicesignaling information and the service list table to generate link layerpackets; and processing the link layer packets into the broadcaststream. This step may be performed by the second module of thetransmission side. The process of encapsulating into the link layerpackets may correspond to the above-described link layer operation. Theprocess of processing the link layer packets into the broadcast streammay correspond to the above-described physical layer processing.

A method of processing service data at a reception side according to anembodiment of the present invention will now be described. This methodis not shown in the figure.

The method of processing the service data at the reception sideaccording to the embodiment of the present invention includes a firstmodule of the reception side receiving a broadcast stream, a secondmodule parsing the broadcast stream to acquire a service list table, athird module accessing service signaling information using the servicelist table, the third module acquiring service data using the servicesignaling information and/or a fourth module reproducing a service usingthe acquired service data.

The methods of processing the service data at the reception sideaccording to the embodiments of the present invention may correspond tothe methods of processing the service data at the transmission sideaccording to the above-described embodiments of the present invention.The methods of processing the service data at the reception side may beperformed by hardware modules (e.g., the first, second, third and fourthmodules of the reception side) corresponding to the modules used in themethod of processing the service data at the transmission side. Themethod of processing the service data at the reception side may haveembodiments corresponding to the embodiments of the method of processingthe service data at the transmission side.

The aforementioned steps may be omitted or replaced by other steps forperforming similar/identical operations according to embodiments.

FIG. 122 is a diagram showing an apparatus for processing service dataaccording to an embodiment of the present invention.

The apparatus for processing the service data according to theembodiment of the present invention may include a first module, a secondmodule and/or a third module of the above-described transmission side.The blocks and modules have been described above.

The apparatus for processing the service data according to theembodiment of the present invention and the modules/blocks includedtherein may perform the embodiments of the method of processing theservice data at the transmission side according to the presentinvention.

The apparatus for processing the service data at the reception sideaccording to an embodiment of the present invention will be described.This apparatus is not shown in the figure.

The apparatus for processing the service data at the reception sideaccording to the embodiment of the present invention may include a firstmodule, a second module, a third module and/or a fourth module of thereception side. The blocks and modules have been described above.

The apparatus for processing the service data at the reception sideaccording to the embodiment of the present invention and themodules/blocks included therein may perform the embodiments of themethod of processing the service data at the reception side according tothe present invention.

The blocks/modules of the above-described apparatus may be processorsfor performing a series of processes stored in a memory and may behardware elements located inside or outside the apparatus according toembodiments.

The aforementioned modules may be omitted or replaced by other steps forperforming similar/identical operations according to embodiments.

Modules or units may be processors executing consecutive processesstored in a memory (or a storage unit). The steps described in theaforementioned embodiments can be performed by hardware/processors.Modules/blocks/units described in the above embodiments can operate ashardware/processors. The methods proposed by the present invention canbe executed as code. Such code can be written on a processor-readablestorage medium and thus can be read by a processor provided by anapparatus.

While the embodiments have been described with reference to respectivedrawings for convenience, embodiments may be combined to implement a newembodiment. In addition, designing computer-readable recording mediumstoring programs for implementing the aforementioned embodiments iswithin the scope of the present invention.

The apparatus and method according to the present invention are notlimited to the configurations and methods of the above-describedembodiments and all or some of the embodiments may be selectivelycombined to obtain various modifications.

The methods proposed by the present invention may be implemented asprocessor-readable code stored in a processor-readable recording mediumincluded in a network device. The processor-readable recording mediumincludes all kinds of recording media storing data readable by aprocessor. Examples of the processor-readable recording medium include aROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical datastorage device and the like, and implementation as carrier waves such astransmission over the Internet. In addition, the processor-readablerecording medium may be distributed to computer systems connectedthrough a network, stored and executed as code readable in a distributedmanner.

Although the preferred embodiments of the present invention have beendisclosed for illustrative purposes, those skilled in the art willappreciate that various modifications, additions and substitutions arepossible, without departing from the scope and spirit of the inventionas disclosed in the accompanying claims. Such modifications should notbe individually understood from the technical spirit or prospect of thepresent invention.

Both apparatus and method inventions are mentioned in this specificationand descriptions of both the apparatus and method inventions may becomplimentarily applied to each other.

Those skilled in the art will appreciate that the present invention maybe carried out in other specific ways than those set forth hereinwithout departing from the spirit and essential characteristics of thepresent invention. Therefore, the scope of the invention should bedetermined by the appended claims and their legal equivalents, not bythe above description, and all changes coming within the meaning andequivalency range of the appended claims are intended to be embracedtherein.

In the specification, both the apparatus invention and the methodinvention are mentioned and description of both the apparatus inventionand the method invention can be applied complimentarily.

MODE FOR INVENTION

Various embodiments have been described in the best mode for carryingout the invention.

INDUSTRIAL APPLICABILITY

The present invention is applied to broadcast signal providing fields.

Various equivalent modifications are possible within the spirit andscope of the present invention, as those skilled in the relevant artwill recognize and appreciate. Accordingly, it is intended that thepresent invention cover the modifications and variations of thisinvention provided they come within the scope of the appended claims andtheir equivalents.

The invention claimed is:
 1. A method of processing service data in atransmitting system, the method comprising: encoding the service data ofa service delivered through one of a real time object delivery overunidirectional transport (ROUTE) session or a MPEG media transportprotocol (MMTP) session; interleaving the encoded service data; encodingfirst signaling data for fast channel scans and service acquisition,wherein the first signaling data includes access information forobtaining second signaling data, service identification information foridentifying the service, and status information for identifying whetherthe service is hidden and wherein the second signaling data providesinformation for discovery and acquisition of the service; andtransmitting a broadcast signal including one or more transport framesthat include the interleaved service data, the encoded first signalingdata, and physical layer signaling data, wherein the physical layersignaling data includes encoding information and interleavinginformation of the service data, wherein the physical layer signalingdata further includes flag information for identifying whether the firstsignaling data is included in a current transport frame, wherein thesecond signaling data is delivered through one of a broadcast network ora broadband network, wherein the access information in the firstsignaling data includes Internet Protocol (IP) address information andUser Data Protocol (UDP) port number information to obtain the secondsignaling data which is delivered through the broadcast network, andwherein the access information in the first signaling data includesuniform resource location information to obtain the second signalingdata which is delivered through the broadband network.
 2. The methodaccording to claim 1, wherein the second signaling data is deliveredthrough a dedicated transport channel whose value is zero when thesecond signaling data is delivered through the broadcast network.
 3. Anapparatus for processing service data in a transmitting system, theapparatus comprising: a first encoder configured to encode the servicedata of a service delivered through one of a real time object deliveryover unidirectional transport (ROUTE) session or a MPEG media transportprotocol (MMTP) session; an interleaver configured to interleave theencoded service data; a second encoder configured to encode firstsignaling data for fast channel scans and service acquisition, whereinthe first signaling data includes access information for obtainingsecond signaling data, service identification information foridentifying the service, and status information for identifying whetherthe service is hidden; a transmitter configured to transmit a broadcastsignal including one or more transport frames that include theinterleaved service data, the encoded first signaling data, and physicallayer signaling data, wherein the physical layer signaling data includesencoding information and interleaving information of the service data,wherein the physical layer signaling data further includes flaginformation for identifying whether the first signaling data is includedin a current transport frame, wherein the second signaling data isdelivered through one of a broadcast network or a broadband network,wherein the access information in the first signaling data includesInternet Protocol (IP) address information and User Data Protocol (UDP)port number information to obtain the second signaling data which isdelivered through the broadcast network, and wherein the accessinformation in the first signaling data includes uniform resourcelocation information to obtain the second signaling data which isdelivered through the broadband network.
 4. The apparatus according toclaim 3, wherein the second signaling data is delivered through adedicated transport channel whose value is zero when the secondsignaling data is delivered through the broadcast network.
 5. A methodof processing data in a receiving system, the method comprising:receiving a broadcast signal including one or more transport frames thatinclude service data of a service, first signaling data for fast channelscans and service acquisition, and physical layer signaling data,wherein the physical layer signaling data includes encoding informationand interleaving information of the service data, wherein the physicallayer signaling data further includes flag information for identifyingwhether the first signaling data is included in a current transportframe, wherein the service data is delivered through one of a real timeobject delivery over unidirectional transport (ROUTE) session or a MPEGmedia transport protocol (MMTP) session, wherein the first signalingdata includes access information for obtaining second signaling data,service identification information for identifying the service, andstatus information for identifying whether the service is hidden, andwherein the second signaling data provides information for discovery andacquisition of the service; decoding the first signaling data;deinterleaving the service data based on the interleaving information ofthe physical layer signaling data; decoding the deinterleaved servicedata based on the encoding information of the physical layer signalingdata; obtaining the second signaling data based on the first signalingdata; and providing the service to a user by discovering and acquiringthe service including the service data based on the second signalingdata, wherein the second signaling data is delivered through one of abroadcast network or a broadband network, wherein the access informationin the first signaling data includes Internet Protocol (IP) addressinformation and User Data Protocol (UDP) port number information toobtain the second signaling data which is delivered through thebroadcast network, and wherein the access information in the firstsignaling data includes uniform resource location information to obtainthe second signaling data which is delivered through the broadbandnetwork.
 6. The method according to claim 5, wherein the secondsignaling data is delivered through a dedicated transport channel whosevalue is zero when the second signaling data is delivered through thebroadcast network.
 7. An apparatus for processing data in a receivingsystem, the apparatus comprising: a tuner configured to receive abroadcast signal including one or more transport frames that includeservice data of a service, first signaling data for fast channel scansand service acquisition, and physical layer signaling data, wherein thephysical layer signaling data includes encoding information andinterleaving information of the service data, wherein the physical layersignaling data further includes flag information for identifying whetherthe first signaling data is included in a current transport frame,wherein the service data is delivered through one of a real time objectdelivery over unidirectional transport (ROUTE) session or a MPEG mediatransport protocol (MMTP) session, wherein the first signaling dataincludes access information for obtaining second signaling data, serviceidentification information for identifying the service, and statusinformation for identifying whether the service is hidden, and whereinthe second signaling data provides information for discovery andacquisition of the service; a first decoder configured to decode thefirst signaling data; a deinterleaver configured to deinterleave theservice data based on the interleaving information of the physical layersignaling data; and a second decoder configured to decode thedeinterleaved service data based on the encoding information of thephysical layer signaling data; a first processor configured to obtainingthe second signaling data based on the first signaling data; and asecond processor configured to providing the service to a user bydiscovering and acquiring the service including the service data basedon the second signaling data, wherein the second signaling data isdelivered through one of a broadcast network or a broadband network,wherein the access information in the first signaling data includesInternet Protocol (IP) address information and User Data Protocol (UDP)port number information to obtain the second signaling data which isdelivered through the broadcast network, and wherein the accessinformation in the first signaling data includes uniform resourcelocation information to obtain the second signaling data which isdelivered through the broadband network.
 8. The apparatus according toclaim 7, wherein the second signaling data is delivered through adedicated transport channel whose value is zero when the secondsignaling data is delivered through the broadcast network.